Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f7f0b3fde1158a87b7672d472005af1c6b4f0d038accbaf1f9f024c34d811ea

Tx prefix hash: 9873871e3072b24ffb2b778cf94b3aeddf09d794f4e3550d4b6bfa6f44206223
Tx public key: d39f73b84c7752792def50d4f59dbc060bab2a64610d466b822fdbc8deb83bd9
Timestamp: 1703109419 Timestamp [UCT]: 2023-12-20 21:56:59 Age [y:d:h:m:s]: 01:126:19:46:45
Block: 917541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351767 RingCT/type: yes/0
Extra: 01d39f73b84c7752792def50d4f59dbc060bab2a64610d466b822fdbc8deb83bd9021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ce4657eab0e1a6b484e47e3297b0da4e074c633514f2133d0b2485414f6ff45 0.600000000000 1375123 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": 917551, "vin": [ { "gen": { "height": 917541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ce4657eab0e1a6b484e47e3297b0da4e074c633514f2133d0b2485414f6ff45" } } ], "extra": [ 1, 211, 159, 115, 184, 76, 119, 82, 121, 45, 239, 80, 212, 245, 157, 188, 6, 11, 171, 42, 100, 97, 13, 70, 107, 130, 47, 219, 200, 222, 184, 59, 217, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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