Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a9df12b789a33a2181da50923dc1b666c870c16dd9e5ac3253540158f7136a

Tx prefix hash: 0060474e816d4ccec64dd3f67115362321153ee07141117871fb721e7297bb7d
Tx public key: ae7e51a31d9682bcd0c5638e2703442ba1d6a0902b774fbcb4163a3c9efcd022
Timestamp: 1700839088 Timestamp [UCT]: 2023-11-24 15:18:08 Age [y:d:h:m:s]: 01:135:15:17:57
Block: 898701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358095 RingCT/type: yes/0
Extra: 01ae7e51a31d9682bcd0c5638e2703442ba1d6a0902b774fbcb4163a3c9efcd022021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.645997004000 dcy

stealth address amount amount idx
00: f69fdd039d64f2d7b486e75645eba603cddb8a5f7678ee48369062a8972db3f7 0.645997004000 1355134 of 0

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": 898711, "vin": [ { "gen": { "height": 898701 } } ], "vout": [ { "amount": 645997004, "target": { "key": "f69fdd039d64f2d7b486e75645eba603cddb8a5f7678ee48369062a8972db3f7" } } ], "extra": [ 1, 174, 126, 81, 163, 29, 150, 130, 188, 208, 197, 99, 142, 39, 3, 68, 43, 161, 214, 160, 144, 43, 119, 79, 188, 180, 22, 58, 60, 158, 252, 208, 34, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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