Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607541a78c1a43f324ec07a55c7eb17f226c5ff7bedb6e61ffb6e69996169578

Tx prefix hash: 494b859c3ef3cc455962b21e5b5b53cbeb9dc7991ee5f6c13ba63f6cbaf675ae
Tx public key: 122de5a0cdcc0326aaee0f30e7b5597e00f1296797462f3d88d7d468dd8728ce
Timestamp: 1735082421 Timestamp [UCT]: 2024-12-24 23:20:21 Age [y:d:h:m:s]: 00:089:03:33:44
Block: 1182479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63480 RingCT/type: yes/0
Extra: 01122de5a0cdcc0326aaee0f30e7b5597e00f1296797462f3d88d7d468dd8728ce0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67dc24ac87d21d2243c62e5dd73b48bfd70e9ee31fd3afca1f17bce63163f1e2 0.600000000000 1668914 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": 1182489, "vin": [ { "gen": { "height": 1182479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67dc24ac87d21d2243c62e5dd73b48bfd70e9ee31fd3afca1f17bce63163f1e2" } } ], "extra": [ 1, 18, 45, 229, 160, 205, 204, 3, 38, 170, 238, 15, 48, 231, 181, 89, 126, 0, 241, 41, 103, 151, 70, 47, 61, 136, 215, 212, 104, 221, 135, 40, 206, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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