Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9388286752c7c0cbac3234252622b0800ffe8b0c7d6d4a3f4243c198e05ab244

Tx prefix hash: 67083fa557eab7677c1dd8e4d654d437ad9d5dc2a1aa4f84397427d2a24bd391
Tx public key: 66a43ac9cf041cbd09cab95724e5313261e00d3a8e9ac5d4320828210b43417f
Timestamp: 1580485307 Timestamp [UCT]: 2020-01-31 15:41:47 Age [y:d:h:m:s]: 04:342:07:05:21
Block: 55917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135831 RingCT/type: yes/0
Extra: 0166a43ac9cf041cbd09cab95724e5313261e00d3a8e9ac5d4320828210b43417f02110000000217786bcf000000000000000000

1 output(s) for total of 400.612587577000 dcy

stealth address amount amount idx
00: 89a6e8bcc5dbac8ac8d860afe1de9789292539a81563050756365e7a2f76cddd 400.612587577000 103152 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 55927, "vin": [ { "gen": { "height": 55917 } } ], "vout": [ { "amount": 400612587577, "target": { "key": "89a6e8bcc5dbac8ac8d860afe1de9789292539a81563050756365e7a2f76cddd" } } ], "extra": [ 1, 102, 164, 58, 201, 207, 4, 28, 189, 9, 202, 185, 87, 36, 229, 49, 50, 97, 224, 13, 58, 142, 154, 197, 212, 50, 8, 40, 33, 11, 67, 65, 127, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8