Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d543aa17ec29399fc8089a4dfb4da5b48692fdcbe921022685d75d5e19c3f48

Tx prefix hash: a377f7c3ec2462c058556da37ea634c7d09c2432a68ce4ab16f20b7cc702f235
Tx public key: 77f8fdd9bdb58412cafa67575d3371bfcdfb25fad4ca56399b5cf33b2414b9fe
Timestamp: 1728514731 Timestamp [UCT]: 2024-10-09 22:58:51 Age [y:d:h:m:s]: 00:174:20:01:47
Block: 1128140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124748 RingCT/type: yes/0
Extra: 0177f8fdd9bdb58412cafa67575d3371bfcdfb25fad4ca56399b5cf33b2414b9fe02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8101b85ee88d964530d4b401a7b36e7111ba630f0bf4c8cf19e6eedf7dad6c7 0.600000000000 1610957 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": 1128150, "vin": [ { "gen": { "height": 1128140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8101b85ee88d964530d4b401a7b36e7111ba630f0bf4c8cf19e6eedf7dad6c7" } } ], "extra": [ 1, 119, 248, 253, 217, 189, 181, 132, 18, 202, 250, 103, 87, 93, 51, 113, 191, 205, 251, 37, 250, 212, 202, 86, 57, 155, 92, 243, 59, 36, 20, 185, 254, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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