Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e7362b83b21dd6080b2a618cc75be2b17010730603a51b58c12eb53326d9c3

Tx prefix hash: 9e3deb32ff3d6166d8bc59833cfc3b07cd0eff5dcfb2eff46b402670e47948c5
Tx public key: 08424159f53391bad56db45a64cf5f27fdb1cce4ba23a41f5f1b37c4fc9da78c
Timestamp: 1706601370 Timestamp [UCT]: 2024-01-30 07:56:10 Age [y:d:h:m:s]: 01:073:07:12:21
Block: 946454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313468 RingCT/type: yes/0
Extra: 0108424159f53391bad56db45a64cf5f27fdb1cce4ba23a41f5f1b37c4fc9da78c02110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06ec91075835fb48db1ae4f6d3cfd3a2d72a62feabc23d049e4a324da865b943 0.600000000000 1404786 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": 946464, "vin": [ { "gen": { "height": 946454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06ec91075835fb48db1ae4f6d3cfd3a2d72a62feabc23d049e4a324da865b943" } } ], "extra": [ 1, 8, 66, 65, 89, 245, 51, 145, 186, 213, 109, 180, 90, 100, 207, 95, 39, 253, 177, 204, 228, 186, 35, 164, 31, 95, 27, 55, 196, 252, 157, 167, 140, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 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