Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89f6418ca79e9ab26c5f068ac8718f9b14f0097097dc4afb08a6c8ef294f8a97

Tx prefix hash: 074cce0f600a9cf9e53515c07fa1313e50ac9ace151a501c5f0f3cb485b206d7
Tx public key: e32f7abaae842ae903a0a030fc57eeedac45872780040808d9cb20e63be0f9ca
Timestamp: 1726511928 Timestamp [UCT]: 2024-09-16 18:38:48 Age [y:d:h:m:s]: 00:160:00:41:43
Block: 1111540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114162 RingCT/type: yes/0
Extra: 01e32f7abaae842ae903a0a030fc57eeedac45872780040808d9cb20e63be0f9ca02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3812b151c568fc5109ab62a62c0f5f575567b56755b25ed75a06e1fc4a711c9 0.600000000000 1590537 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": 1111550, "vin": [ { "gen": { "height": 1111540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3812b151c568fc5109ab62a62c0f5f575567b56755b25ed75a06e1fc4a711c9" } } ], "extra": [ 1, 227, 47, 122, 186, 174, 132, 42, 233, 3, 160, 160, 48, 252, 87, 238, 237, 172, 69, 135, 39, 128, 4, 8, 8, 217, 203, 32, 230, 59, 224, 249, 202, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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