Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f958e3e6f56bfb6dff1df189f95fada8f2148722d2c2d500f8a3472a007294

Tx prefix hash: bac8c2fe6d6fa8eeefb0c315eebb92245b650a302babc1fb5aa950f4f9327d76
Tx public key: ed2d547d9277f066213b5034b925401bafafe5f83db1dd8f240ae77aefb2ddc3
Timestamp: 1765643187 Timestamp [UCT]: 2025-12-13 16:26:27 Age [y:d:h:m:s]: 00:026:12:23:20
Block: 1432828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18983 RingCT/type: yes/0
Extra: 01ed2d547d9277f066213b5034b925401bafafe5f83db1dd8f240ae77aefb2ddc302110000000a70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9524b6feccaccb95f92eb0a7db3e851d1bf7f2bf900b757bbea2c07cecb91f0f 0.600000000000 1921607 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": 1432838, "vin": [ { "gen": { "height": 1432828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9524b6feccaccb95f92eb0a7db3e851d1bf7f2bf900b757bbea2c07cecb91f0f" } } ], "extra": [ 1, 237, 45, 84, 125, 146, 119, 240, 102, 33, 59, 80, 52, 185, 37, 64, 27, 175, 175, 229, 248, 61, 177, 221, 143, 36, 10, 231, 122, 239, 178, 221, 195, 2, 17, 0, 0, 0, 10, 112, 96, 157, 3, 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