Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222f0ef4b844af5cec9339287dc9c1dfb3ca67cf2c3a36726f7703916caf9f8c

Tx prefix hash: 06bea3453ca4c2b6330b3bc36a2ebedf427966f21096d99f9df32a1cfabbf2b0
Tx public key: d80ea885adac5774424866ee55ab58bee2b1f7af2e5a1ec76c984be8e627c865
Timestamp: 1717110236 Timestamp [UCT]: 2024-05-30 23:03:56 Age [y:d:h:m:s]: 00:350:17:58:34
Block: 1033593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250704 RingCT/type: yes/0
Extra: 01d80ea885adac5774424866ee55ab58bee2b1f7af2e5a1ec76c984be8e627c8650211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2c4ab046311841fdb92f5bf366f488a4f352eddc8fc01634b37444b09bf860 0.600000000000 1502064 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": 1033603, "vin": [ { "gen": { "height": 1033593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2c4ab046311841fdb92f5bf366f488a4f352eddc8fc01634b37444b09bf860" } } ], "extra": [ 1, 216, 14, 168, 133, 173, 172, 87, 116, 66, 72, 102, 238, 85, 171, 88, 190, 226, 177, 247, 175, 46, 90, 30, 199, 108, 152, 75, 232, 230, 39, 200, 101, 2, 17, 0, 0, 0, 5, 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