Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4abfe01e625a1ba0108ea15f37253d7ee4ab42c5ceef327f72b7021950d4a3a2

Tx prefix hash: bd5530c6c06f705cc45f5e148e453cc6eb3c2648d1b23eb704adf3fd1679e9b6
Tx public key: de85262a8129928bd3f78c6ed017dad9d6a986cccc2898ef624dce53fe983bb9
Timestamp: 1719371134 Timestamp [UCT]: 2024-06-26 03:05:34 Age [y:d:h:m:s]: 00:285:15:33:28
Block: 1052331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204110 RingCT/type: yes/0
Extra: 01de85262a8129928bd3f78c6ed017dad9d6a986cccc2898ef624dce53fe983bb90211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a7652817992ce0c712bef306ed2eb5c0336cc8f3a045d936cab5527b06221fe 0.600000000000 1522654 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": 1052341, "vin": [ { "gen": { "height": 1052331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a7652817992ce0c712bef306ed2eb5c0336cc8f3a045d936cab5527b06221fe" } } ], "extra": [ 1, 222, 133, 38, 42, 129, 41, 146, 139, 211, 247, 140, 110, 208, 23, 218, 217, 214, 169, 134, 204, 204, 40, 152, 239, 98, 77, 206, 83, 254, 152, 59, 185, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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