Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539be80f388ce846e001d3fa8ec5b13a15174229e691822719310a7620386d12

Tx prefix hash: 59e2453bd39f9a238db2dd0d410f18a67e33993d8585fd3d2b6d82ba97b82503
Tx public key: 6c50ce1ed4f83e562c64a3d4de182b5c997714aa6c76790842c72aa8af442289
Timestamp: 1726550609 Timestamp [UCT]: 2024-09-17 05:23:29 Age [y:d:h:m:s]: 00:058:21:44:17
Block: 1111858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42101 RingCT/type: yes/0
Extra: 016c50ce1ed4f83e562c64a3d4de182b5c997714aa6c76790842c72aa8af44228902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b7425bf8b4854fcccbc5fdd091a321d531434551546d2f8f1eaf4ec6d7ea7a 0.600000000000 1590969 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": 1111868, "vin": [ { "gen": { "height": 1111858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b7425bf8b4854fcccbc5fdd091a321d531434551546d2f8f1eaf4ec6d7ea7a" } } ], "extra": [ 1, 108, 80, 206, 30, 212, 248, 62, 86, 44, 100, 163, 212, 222, 24, 43, 92, 153, 119, 20, 170, 108, 118, 121, 8, 66, 199, 42, 168, 175, 68, 34, 137, 2, 17, 0, 0, 0, 2, 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