Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5f1e30e74f59d32239e7dadcfc435976712a11fac8fdfb05b60f74bd03370f

Tx prefix hash: 347d5a0cc3d3fdc47c09b0c761a632c4caabd248bd35ca24cdb62298d1f1f7df
Tx public key: 5dc958d510876095b6b2ffbdf8edeb158457f1c8ce46b6ce24ef2a23c9b24dd2
Timestamp: 1650084697 Timestamp [UCT]: 2022-04-16 04:51:37 Age [y:d:h:m:s]: 03:198:19:53:27
Block: 481168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 920412 RingCT/type: yes/0
Extra: 015dc958d510876095b6b2ffbdf8edeb158457f1c8ce46b6ce24ef2a23c9b24dd2021100000002d3fcec30000000000000000000

1 output(s) for total of 15.620355252000 dcy

stealth address amount amount idx
00: 5f32ea9e9a74eea6fa4a85145d4bee4b4b1880a63689e1d4cddd5bf19457826c 15.620355252000 902375 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": 481178, "vin": [ { "gen": { "height": 481168 } } ], "vout": [ { "amount": 15620355252, "target": { "key": "5f32ea9e9a74eea6fa4a85145d4bee4b4b1880a63689e1d4cddd5bf19457826c" } } ], "extra": [ 1, 93, 201, 88, 213, 16, 135, 96, 149, 182, 178, 255, 189, 248, 237, 235, 21, 132, 87, 241, 200, 206, 70, 182, 206, 36, 239, 42, 35, 201, 178, 77, 210, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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