Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb64fbc616922fcc07b7a7950c75e79804a1f68714153d8f1bdf0e30018b7e12

Tx prefix hash: fbd5fb78ac9d376495664233ee60448b4b691f8fa1d1e94fec629f8d2973c6ea
Tx public key: c304dd44bd25e77e99b7cff3ef898fb68996ced11ae9446b57157e3b8370da23
Timestamp: 1706648515 Timestamp [UCT]: 2024-01-30 21:01:55 Age [y:d:h:m:s]: 00:362:07:23:57
Block: 946845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259143 RingCT/type: yes/0
Extra: 01c304dd44bd25e77e99b7cff3ef898fb68996ced11ae9446b57157e3b8370da230211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89dc3fadfe7595b7b1f5077c253db1995a2eee4f66805e11f2c41e28252d0bc4 0.600000000000 1405185 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": 946855, "vin": [ { "gen": { "height": 946845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89dc3fadfe7595b7b1f5077c253db1995a2eee4f66805e11f2c41e28252d0bc4" } } ], "extra": [ 1, 195, 4, 221, 68, 189, 37, 231, 126, 153, 183, 207, 243, 239, 137, 143, 182, 137, 150, 206, 209, 26, 233, 68, 107, 87, 21, 126, 59, 131, 112, 218, 35, 2, 17, 0, 0, 0, 2, 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