Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4798d570de93b1137b012a9fa63a927aa164a466652021dc815e0bd0f7b66ea

Tx prefix hash: 5f9b8794af38e52acf2e2463d78c3df72dbdf70d86bae7b2a9dfa0c520cb8b7c
Tx public key: dc3215204089c8e8de624f60647ae8f7d6782d8926c3adb0ad4971b2b9c5275b
Timestamp: 1767121987 Timestamp [UCT]: 2025-12-30 19:13:07 Age [y:d:h:m:s]: 00:009:10:39:45
Block: 1445075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6772 RingCT/type: yes/0
Extra: 01dc3215204089c8e8de624f60647ae8f7d6782d8926c3adb0ad4971b2b9c5275b02110000000649d73e98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc66bdf033afcab08c8de7ebf455acbb7c5f8d5e889982e2f2d4eec855f2066 0.600000000000 1934013 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": 1445085, "vin": [ { "gen": { "height": 1445075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc66bdf033afcab08c8de7ebf455acbb7c5f8d5e889982e2f2d4eec855f2066" } } ], "extra": [ 1, 220, 50, 21, 32, 64, 137, 200, 232, 222, 98, 79, 96, 100, 122, 232, 247, 214, 120, 45, 137, 38, 195, 173, 176, 173, 73, 113, 178, 185, 197, 39, 91, 2, 17, 0, 0, 0, 6, 73, 215, 62, 152, 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