Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5657470482d5bf11bd419bf7f7f1e560c9f3b258b54ebc02a39145d5fedc696

Tx prefix hash: 6b642d1f83e92c44ae6890d8a3434638d598e92a1c3247c874fca8c3c17e1a64
Tx public key: fb5e6082a9dd5aeca274598d789ed602f5a2df9170be1ffc2520cb3ff9b7d02b
Timestamp: 1764005587 Timestamp [UCT]: 2025-11-24 17:33:07 Age [y:d:h:m:s]: 00:002:19:33:18
Block: 1419257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2017 RingCT/type: yes/0
Extra: 01fb5e6082a9dd5aeca274598d789ed602f5a2df9170be1ffc2520cb3ff9b7d02b02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8caf1eb7b3c4fc665fa1b10af1888c2a466db02dda6a484dec168ba124a6c054 0.600000000000 1907792 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": 1419267, "vin": [ { "gen": { "height": 1419257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8caf1eb7b3c4fc665fa1b10af1888c2a466db02dda6a484dec168ba124a6c054" } } ], "extra": [ 1, 251, 94, 96, 130, 169, 221, 90, 236, 162, 116, 89, 141, 120, 158, 214, 2, 245, 162, 223, 145, 112, 190, 31, 252, 37, 32, 203, 63, 249, 183, 208, 43, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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