Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395ceea2e2c851bb33eb8c88e6a7d5d9166d4eef9cfd97f68bae85607103f82b

Tx prefix hash: d3455141271c21face90837191699f73522fa96534459bc18185fa84d1414a36
Tx public key: 5c1b45f665c751de4ca5f491d79e1ccd7e341e42c6e60435c3b23025b24e7163
Timestamp: 1723979843 Timestamp [UCT]: 2024-08-18 11:17:23 Age [y:d:h:m:s]: 00:230:14:40:26
Block: 1090554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164686 RingCT/type: yes/0
Extra: 015c1b45f665c751de4ca5f491d79e1ccd7e341e42c6e60435c3b23025b24e716302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af08de56f7096b9b42de409b60b13d5e4a83eb2fdddf400b28cdb737b51916a 0.600000000000 1565177 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": 1090564, "vin": [ { "gen": { "height": 1090554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af08de56f7096b9b42de409b60b13d5e4a83eb2fdddf400b28cdb737b51916a" } } ], "extra": [ 1, 92, 27, 69, 246, 101, 199, 81, 222, 76, 165, 244, 145, 215, 158, 28, 205, 126, 52, 30, 66, 198, 230, 4, 53, 195, 178, 48, 37, 178, 78, 113, 99, 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