Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b01155788783ef374c399a103351de01ea1e1e4be285fa2693ee344c8f5fd1

Tx prefix hash: 566d2f5ef04bbe07195ce499f6326c8285f00bb9dd07b967e41d0c9753eeaece
Tx public key: 69487f0b6ffbe9b9253ae89492f4ddcdf9c41b00d042fbcd9cd9e529868400d6
Timestamp: 1704585331 Timestamp [UCT]: 2024-01-06 23:55:31 Age [y:d:h:m:s]: 01:108:06:55:18
Block: 929744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338521 RingCT/type: yes/0
Extra: 0169487f0b6ffbe9b9253ae89492f4ddcdf9c41b00d042fbcd9cd9e529868400d60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd081d8126c0eac19f2f7520a23091dcbd19307dee665a2d57834ae04b65f68 0.600000000000 1387620 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": 929754, "vin": [ { "gen": { "height": 929744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd081d8126c0eac19f2f7520a23091dcbd19307dee665a2d57834ae04b65f68" } } ], "extra": [ 1, 105, 72, 127, 11, 111, 251, 233, 185, 37, 58, 232, 148, 146, 244, 221, 205, 249, 196, 27, 0, 208, 66, 251, 205, 156, 217, 229, 41, 134, 132, 0, 214, 2, 17, 0, 0, 0, 3, 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