Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 496cbc2917425e2977455064fbcd52da7b3e749cb0cc0ced2f40fa835f916b19

Tx prefix hash: 1892b1e6f57a413931088bbc02762de0a3654fb687e1598b79dbac2e9ae81523
Tx public key: b3482b8b4e3dd00a2b0c76d176676f079f0af7990720cf4084d5567480279679
Timestamp: 1728762510 Timestamp [UCT]: 2024-10-12 19:48:30 Age [y:d:h:m:s]: 00:164:16:48:04
Block: 1130201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117477 RingCT/type: yes/0
Extra: 01b3482b8b4e3dd00a2b0c76d176676f079f0af7990720cf4084d556748027967902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941bc2ff6ca3dc1f3d4f24bea6a5b67cdc4927aac8c7d17ab6a29a451cd2a7f7 0.600000000000 1613074 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": 1130211, "vin": [ { "gen": { "height": 1130201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941bc2ff6ca3dc1f3d4f24bea6a5b67cdc4927aac8c7d17ab6a29a451cd2a7f7" } } ], "extra": [ 1, 179, 72, 43, 139, 78, 61, 208, 10, 43, 12, 118, 209, 118, 103, 111, 7, 159, 10, 247, 153, 7, 32, 207, 64, 132, 213, 86, 116, 128, 39, 150, 121, 2, 17, 0, 0, 0, 1, 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