Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5fbde9e5cf7340a13bd2fc14ba759108499b651d33a94ed367810bb9b1c0454

Tx prefix hash: 916608e781c9b0d1f2be6b4742e126dc9087f839fd3cb5b2ea1182a8ecce17c9
Tx public key: 9151e783fd85f4753fb9f0f332720e8a7a3611f354b13e3caca1ba67f7d96aa2
Timestamp: 1712702126 Timestamp [UCT]: 2024-04-09 22:35:26 Age [y:d:h:m:s]: 01:007:07:05:56
Block: 997029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266187 RingCT/type: yes/0
Extra: 019151e783fd85f4753fb9f0f332720e8a7a3611f354b13e3caca1ba67f7d96aa202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 002a2d07664d839265bc65fc7bd2c2a3765d965e4e77b31fff30107b7b0348a8 0.600000000000 1457457 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": 997039, "vin": [ { "gen": { "height": 997029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "002a2d07664d839265bc65fc7bd2c2a3765d965e4e77b31fff30107b7b0348a8" } } ], "extra": [ 1, 145, 81, 231, 131, 253, 133, 244, 117, 63, 185, 240, 243, 50, 114, 14, 138, 122, 54, 17, 243, 84, 177, 62, 60, 172, 161, 186, 103, 247, 217, 106, 162, 2, 17, 0, 0, 0, 4, 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