Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add0f2096162c1b297803b4d5ee7c36dabec5c75d86f0db91064594f969dbe91

Tx prefix hash: de0c1562b79d0aed47990ee2830268cfaa3a963ebb79493e31fbae91a7f8ecee
Tx public key: 8eb899e2a4fd77125b5c952ee99a99b829113a7cf2fbac3f6b4aaf0fc23754dc
Timestamp: 1717170372 Timestamp [UCT]: 2024-05-31 15:46:12 Age [y:d:h:m:s]: 00:310:23:25:28
Block: 1034107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222243 RingCT/type: yes/0
Extra: 018eb899e2a4fd77125b5c952ee99a99b829113a7cf2fbac3f6b4aaf0fc23754dc021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7521b821420dd69f290183e2459f5fe77245fedb1536b1ef971397a38ed75e6a 0.600000000000 1502582 of 15

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": 1034117, "vin": [ { "gen": { "height": 1034107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7521b821420dd69f290183e2459f5fe77245fedb1536b1ef971397a38ed75e6a" } } ], "extra": [ 1, 142, 184, 153, 226, 164, 253, 119, 18, 91, 92, 149, 46, 233, 154, 153, 184, 41, 17, 58, 124, 242, 251, 172, 63, 107, 74, 175, 15, 194, 55, 84, 220, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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