Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36604b553033e322643baf89375b691d05d6800b05d14f51733b1ca3beedf31c

Tx prefix hash: 57bb7ae0e361bb90b5e44dcc6fe4a6b266824ec56089f1b3981a421c6a8c3022
Tx public key: f776db7c2f473593d611bd73ce1be5b53cb53e45b3b1027cddc1daf3b748d888
Timestamp: 1764159516 Timestamp [UCT]: 2025-11-26 12:18:36 Age [y:d:h:m:s]: 00:000:23:08:56
Block: 1420529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696 RingCT/type: yes/0
Extra: 01f776db7c2f473593d611bd73ce1be5b53cb53e45b3b1027cddc1daf3b748d8880211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 216abfc09c8351daf1b5ff6dc03cfab0734a8f2a84771b0da14bae39844feb66 0.600000000000 1909074 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": 1420539, "vin": [ { "gen": { "height": 1420529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "216abfc09c8351daf1b5ff6dc03cfab0734a8f2a84771b0da14bae39844feb66" } } ], "extra": [ 1, 247, 118, 219, 124, 47, 71, 53, 147, 214, 17, 189, 115, 206, 27, 229, 181, 60, 181, 62, 69, 179, 177, 2, 124, 221, 193, 218, 243, 183, 72, 216, 136, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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