Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ccb947baba92d095f4b503aafc83fef101673f983e30a217e24d0c85b99679d

Tx prefix hash: 8c64851c357c539d952b26462978264a274e95256b7ae1f89130767052df5a1b
Tx public key: 99dc540b17f8927c41afe0d33b84e02ac2f3896d27ac8b26a18c984f93555983
Timestamp: 1751832605 Timestamp [UCT]: 2025-07-06 20:10:05 Age [y:d:h:m:s]: 00:136:18:20:04
Block: 1320151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96138 RingCT/type: yes/0
Extra: 0199dc540b17f8927c41afe0d33b84e02ac2f3896d27ac8b26a18c984f93555983021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c653cd08f2dfeb424f788b649eb0449e362fc50238d9fd3f07f7155b41a3ade 0.600000000000 1807846 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": 1320161, "vin": [ { "gen": { "height": 1320151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c653cd08f2dfeb424f788b649eb0449e362fc50238d9fd3f07f7155b41a3ade" } } ], "extra": [ 1, 153, 220, 84, 11, 23, 248, 146, 124, 65, 175, 224, 211, 59, 132, 224, 42, 194, 243, 137, 109, 39, 172, 139, 38, 161, 140, 152, 79, 147, 85, 89, 131, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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