Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e4a57aaa6c8f68a818b9a7d818edab57ba06e35590ecc0045c4c9290b7356d3

Tx prefix hash: 73ef1858516fe6044ef866fb8a7074579c6289134b277d4924d962e813cb1c74
Tx public key: 4491a10daf1642e023c8d4fc644a1441558e47df5664469f3d027ed763d005a1
Timestamp: 1703608485 Timestamp [UCT]: 2023-12-26 16:34:45 Age [y:d:h:m:s]: 01:135:02:06:33
Block: 921664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357679 RingCT/type: yes/0
Extra: 014491a10daf1642e023c8d4fc644a1441558e47df5664469f3d027ed763d005a102110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10a08bd2c4c150d2032a6f9e4541490d21c5c10cf054af6ec63464d4a6ebb921 0.600000000000 1379354 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": 921674, "vin": [ { "gen": { "height": 921664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10a08bd2c4c150d2032a6f9e4541490d21c5c10cf054af6ec63464d4a6ebb921" } } ], "extra": [ 1, 68, 145, 161, 13, 175, 22, 66, 224, 35, 200, 212, 252, 100, 74, 20, 65, 85, 142, 71, 223, 86, 100, 70, 159, 61, 2, 126, 215, 99, 208, 5, 161, 2, 17, 0, 0, 0, 10, 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