Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60511a2d7e414520f2b5c51985e4d135e3b40ef24810b07e2db45423c947dbb

Tx prefix hash: 64640f9f5b4404a2a2ae301bf85c5822bad376b8aee3c472403aa96aef7fcee7
Tx public key: d315d6d1ceee133d68811ddf66ecd3093cac36a5d69329d663865ee6e70d426c
Timestamp: 1711660196 Timestamp [UCT]: 2024-03-28 21:09:56 Age [y:d:h:m:s]: 00:363:23:14:53
Block: 988429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260196 RingCT/type: yes/0
Extra: 01d315d6d1ceee133d68811ddf66ecd3093cac36a5d69329d663865ee6e70d426c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d179bbf5cc90a48271ee34e4b696a7c05d55d8a925b97946f142081b6b609f2 0.600000000000 1448708 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": 988439, "vin": [ { "gen": { "height": 988429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d179bbf5cc90a48271ee34e4b696a7c05d55d8a925b97946f142081b6b609f2" } } ], "extra": [ 1, 211, 21, 214, 209, 206, 238, 19, 61, 104, 129, 29, 223, 102, 236, 211, 9, 60, 172, 54, 165, 214, 147, 41, 214, 99, 134, 94, 230, 231, 13, 66, 108, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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