Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c01f389109459b4338b9b1f0a89687067bc33ba52e549d852a0d5e8caca6bae

Tx prefix hash: a7db353e8ceef45ee8997f432b2b70b90a5563dcba88842349b09d1263267f8d
Tx public key: 04d3f6230be0d7abdc61c6e65deefeba6012cb1cb5317954803e244490adfeee
Timestamp: 1582293045 Timestamp [UCT]: 2020-02-21 13:50:45 Age [y:d:h:m:s]: 04:315:11:42:01
Block: 69545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117994 RingCT/type: yes/0
Extra: 0104d3f6230be0d7abdc61c6e65deefeba6012cb1cb5317954803e244490adfeee02110000000112c4732d000000000000000000

1 output(s) for total of 361.051663127000 dcy

stealth address amount amount idx
00: fbe1f8053add723e0276d82aeb64db67273f464ee5ad399a8aaade76cdb393c1 361.051663127000 128273 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": 69555, "vin": [ { "gen": { "height": 69545 } } ], "vout": [ { "amount": 361051663127, "target": { "key": "fbe1f8053add723e0276d82aeb64db67273f464ee5ad399a8aaade76cdb393c1" } } ], "extra": [ 1, 4, 211, 246, 35, 11, 224, 215, 171, 220, 97, 198, 230, 93, 238, 254, 186, 96, 18, 203, 28, 181, 49, 121, 84, 128, 62, 36, 68, 144, 173, 254, 238, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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