Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e850df5a3c86158144163c431855ffab81650b66d171084db21251c51f742631

Tx prefix hash: 6a1aff5dd7bc90159f38aed44da14c30fa02ad88f2469c53d78cd065e58e490e
Tx public key: 1573b676e4616d761779b66e370c6c183bd4e9a32d3cfff0d1c048bdd8a82104
Timestamp: 1694867672 Timestamp [UCT]: 2023-09-16 12:34:32 Age [y:d:h:m:s]: 01:129:12:44:11
Block: 849386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353851 RingCT/type: yes/0
Extra: 011573b676e4616d761779b66e370c6c183bd4e9a32d3cfff0d1c048bdd8a8210402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.941091049000 dcy

stealth address amount amount idx
00: a506afcf44136e70d921e8d7cb72c6ca311b74ade805a7496c9f65b51fc3b892 0.941091049000 1303050 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": 849396, "vin": [ { "gen": { "height": 849386 } } ], "vout": [ { "amount": 941091049, "target": { "key": "a506afcf44136e70d921e8d7cb72c6ca311b74ade805a7496c9f65b51fc3b892" } } ], "extra": [ 1, 21, 115, 182, 118, 228, 97, 109, 118, 23, 121, 182, 110, 55, 12, 108, 24, 59, 212, 233, 163, 45, 60, 255, 240, 209, 192, 72, 189, 216, 168, 33, 4, 2, 17, 0, 0, 0, 5, 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