Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2ba3b92bd1b79a97925babc59d0c5f1c06eb866441c21131165beac6e9123d

Tx prefix hash: e946e34d391b568b051e3081666b1f490c695d5d597fd92067e74870edc38280
Tx public key: 133f062b5aea31e5d60477d98db0eef30f57f902df176a0bac1d9b81ecb485c7
Timestamp: 1710652554 Timestamp [UCT]: 2024-03-17 05:15:54 Age [y:d:h:m:s]: 00:364:04:25:47
Block: 980081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260390 RingCT/type: yes/0
Extra: 01133f062b5aea31e5d60477d98db0eef30f57f902df176a0bac1d9b81ecb485c702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5a7661b8089528485b5d54d7dc499f0be5ada5516ea9ee44d8f4e1dfeb8bcf 0.600000000000 1440140 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": 980091, "vin": [ { "gen": { "height": 980081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5a7661b8089528485b5d54d7dc499f0be5ada5516ea9ee44d8f4e1dfeb8bcf" } } ], "extra": [ 1, 19, 63, 6, 43, 90, 234, 49, 229, 214, 4, 119, 217, 141, 176, 238, 243, 15, 87, 249, 2, 223, 23, 106, 11, 172, 29, 155, 129, 236, 180, 133, 199, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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