Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f693d8a636f5c431d7ad43e36683fc776feb3027eefadfcab2a43dcab2f8ee

Tx prefix hash: 96369094a9afe64de043c519a5e381c2e7eb375b6332e13129a2f3cd21fb68e4
Tx public key: 22a51280832a4ea8600b3eb17609d0f5fe887da109833f7364cd9f2585b4df89
Timestamp: 1710843762 Timestamp [UCT]: 2024-03-19 10:22:42 Age [y:d:h:m:s]: 01:001:05:44:16
Block: 981665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261861 RingCT/type: yes/0
Extra: 0122a51280832a4ea8600b3eb17609d0f5fe887da109833f7364cd9f2585b4df8902110000002152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 016213dae1b6285fc91be6369070af318ef5d4c9d42d08ecb24d6d0de8db97dc 0.600000000000 1441762 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": 981675, "vin": [ { "gen": { "height": 981665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016213dae1b6285fc91be6369070af318ef5d4c9d42d08ecb24d6d0de8db97dc" } } ], "extra": [ 1, 34, 165, 18, 128, 131, 42, 78, 168, 96, 11, 62, 177, 118, 9, 208, 245, 254, 136, 125, 161, 9, 131, 63, 115, 100, 205, 159, 37, 133, 180, 223, 137, 2, 17, 0, 0, 0, 33, 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