Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f44414a02b0043e94bc0498b9af7c24dde622b2c4b0962ccc357a378fb5990

Tx prefix hash: e2a426f3ad68ec9599c7b3e6a6ab24e74d7d23473d54acb0f29dcf268267cd7e
Tx public key: 1fa1d26cf5c3438b4725e3819032f3fddd6bf81e1f3efb01bea94d86f7760108
Timestamp: 1749069470 Timestamp [UCT]: 2025-06-04 20:37:50 Age [y:d:h:m:s]: 00:241:22:24:27
Block: 1298016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170513 RingCT/type: yes/0
Extra: 011fa1d26cf5c3438b4725e3819032f3fddd6bf81e1f3efb01bea94d86f776010802110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d25e9d9b6e1ad40b5e0fd7754eb39f74204cf088e999364dea5979ae71a6c4 0.600000000000 1785539 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": 1298026, "vin": [ { "gen": { "height": 1298016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d25e9d9b6e1ad40b5e0fd7754eb39f74204cf088e999364dea5979ae71a6c4" } } ], "extra": [ 1, 31, 161, 210, 108, 245, 195, 67, 139, 71, 37, 227, 129, 144, 50, 243, 253, 221, 107, 248, 30, 31, 62, 251, 1, 190, 169, 77, 134, 247, 118, 1, 8, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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