Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db371cb420f2500a210e8f47fa6b62d4c24f812d7f54bd4e9131a7624e6c6138

Tx prefix hash: b796afd150d82e54a6d9908d5bfce3884039858b1d37fb8a9ea0f39a7a935cfe
Tx public key: 8ad2731848a0be64580bd31f765423d31f08ddeeb66299d97ecfb8d747e57dc3
Timestamp: 1689555342 Timestamp [UCT]: 2023-07-17 00:55:42 Age [y:d:h:m:s]: 01:298:18:31:38
Block: 805411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474666 RingCT/type: yes/0
Extra: 018ad2731848a0be64580bd31f765423d31f08ddeeb66299d97ecfb8d747e57dc302110000000a33af99f4000000000000000000

1 output(s) for total of 1.316252281000 dcy

stealth address amount amount idx
00: 69b0ff3952787b71772d30e9384c3aee4dc04b9f388311a8f96eb5f09bd4a681 1.316252281000 1256638 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": 805421, "vin": [ { "gen": { "height": 805411 } } ], "vout": [ { "amount": 1316252281, "target": { "key": "69b0ff3952787b71772d30e9384c3aee4dc04b9f388311a8f96eb5f09bd4a681" } } ], "extra": [ 1, 138, 210, 115, 24, 72, 160, 190, 100, 88, 11, 211, 31, 118, 84, 35, 211, 31, 8, 221, 238, 182, 98, 153, 217, 126, 207, 184, 215, 71, 229, 125, 195, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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