Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3d1824490b531474f3b7b1648591f52a0785b9a13599103daf2ab0fef731bd

Tx prefix hash: 0e9bf0ff16e3c209941d9f863e9d64097c1028b05972a98c1b0bc3c6e832cabc
Tx public key: f6077610335acd6fbc7e4405526c72343f0d903286d975043695bd44ce1a6aef
Timestamp: 1710627247 Timestamp [UCT]: 2024-03-16 22:14:07 Age [y:d:h:m:s]: 01:029:02:08:59
Block: 979865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281761 RingCT/type: yes/0
Extra: 01f6077610335acd6fbc7e4405526c72343f0d903286d975043695bd44ce1a6aef0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d536eb282c56b2e0d829ad73e8139b1c3eca0be737a2d29a9ba19721cd0d985b 0.600000000000 1439920 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": 979875, "vin": [ { "gen": { "height": 979865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d536eb282c56b2e0d829ad73e8139b1c3eca0be737a2d29a9ba19721cd0d985b" } } ], "extra": [ 1, 246, 7, 118, 16, 51, 90, 205, 111, 188, 126, 68, 5, 82, 108, 114, 52, 63, 13, 144, 50, 134, 217, 117, 4, 54, 149, 189, 68, 206, 26, 106, 239, 2, 17, 0, 0, 0, 5, 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