Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbd16a8f9f20c03516c8d9274a5dba3f3c8436a8d5c95fc8f0dd6b1bc2fed61

Tx prefix hash: 82fa7d978a6068d85d886066b2c898eee3f4667fb47205ea0d3a851360a65344
Tx public key: e49be8c911453caf614dfe4baa4240579fe36987941ac30c763cb63751b0ac01
Timestamp: 1707500986 Timestamp [UCT]: 2024-02-09 17:49:46 Age [y:d:h:m:s]: 01:057:14:43:02
Block: 953922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302222 RingCT/type: yes/0
Extra: 01e49be8c911453caf614dfe4baa4240579fe36987941ac30c763cb63751b0ac010211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa6e32a2b670342296f893d9d7e2524dcb6906dba146bc9d1aa6e0c61e90990c 0.600000000000 1413194 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": 953932, "vin": [ { "gen": { "height": 953922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa6e32a2b670342296f893d9d7e2524dcb6906dba146bc9d1aa6e0c61e90990c" } } ], "extra": [ 1, 228, 155, 232, 201, 17, 69, 60, 175, 97, 77, 254, 75, 170, 66, 64, 87, 159, 227, 105, 135, 148, 26, 195, 12, 118, 60, 182, 55, 81, 176, 172, 1, 2, 17, 0, 0, 0, 2, 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