Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc845178945ec0add8bc0ed3d2ed58128ba692bdec2d6c42c3b0003719528e3c

Tx prefix hash: c773d7eabf41f6cdd84d2374ad8b2da2ea8db207207b3926a77d61068580913e
Tx public key: 2eef3e0c74466fe34d27a540f5dba2d7ca0c88b1a8be4cbdfd0c5373adc6fdb6
Timestamp: 1684654502 Timestamp [UCT]: 2023-05-21 07:35:02 Age [y:d:h:m:s]: 01:313:04:02:16
Block: 764779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485029 RingCT/type: yes/0
Extra: 012eef3e0c74466fe34d27a540f5dba2d7ca0c88b1a8be4cbdfd0c5373adc6fdb602110000000175e3f0e9000000000000000000

1 output(s) for total of 1.794609158000 dcy

stealth address amount amount idx
00: a5b44a368871e2a556330de3f4e10ed651c1e99afa7cfe26730fd331bd92ab24 1.794609158000 1213732 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": 764789, "vin": [ { "gen": { "height": 764779 } } ], "vout": [ { "amount": 1794609158, "target": { "key": "a5b44a368871e2a556330de3f4e10ed651c1e99afa7cfe26730fd331bd92ab24" } } ], "extra": [ 1, 46, 239, 62, 12, 116, 70, 111, 227, 77, 39, 165, 64, 245, 219, 162, 215, 202, 12, 136, 177, 168, 190, 76, 189, 253, 12, 83, 115, 173, 198, 253, 182, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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