Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae564e6d30f6669726ab307a4ab656ff10994937a77fe11104ead6c5bcb8dafd

Tx prefix hash: a511a6c7136ccfc0ebea81567d679b2fccb5b0bd0af87a95dfaa95d8b9dea7c2
Tx public key: f2a3c3f2e975a5d20f42bf86064e24d92e235469f76dae96b06eab29ab6a6493
Timestamp: 1709862815 Timestamp [UCT]: 2024-03-08 01:53:35 Age [y:d:h:m:s]: 01:021:04:16:27
Block: 973515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276128 RingCT/type: yes/0
Extra: 01f2a3c3f2e975a5d20f42bf86064e24d92e235469f76dae96b06eab29ab6a649302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e56ad67e601852a8793811f1e79baff2256fa57a78d9356a184bc5ba809705f 0.600000000000 1433450 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": 973525, "vin": [ { "gen": { "height": 973515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e56ad67e601852a8793811f1e79baff2256fa57a78d9356a184bc5ba809705f" } } ], "extra": [ 1, 242, 163, 195, 242, 233, 117, 165, 210, 15, 66, 191, 134, 6, 78, 36, 217, 46, 35, 84, 105, 247, 109, 174, 150, 176, 110, 171, 41, 171, 106, 100, 147, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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