Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26040e307fab8a685cad3bbc9fcd8cdae43e951c9ab74f944f6e581b83bd5ea

Tx prefix hash: c6f412d98aea3374eedf195b7fe154046da35da0f53b680ace740fdb05aad2ea
Tx public key: 92732de81f3a36ea8b675de616260c2c97d888d3f2decb82a7325bbabf06c840
Timestamp: 1759050166 Timestamp [UCT]: 2025-09-28 09:02:46 Age [y:d:h:m:s]: 00:009:13:43:47
Block: 1378179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6848 RingCT/type: yes/0
Extra: 0192732de81f3a36ea8b675de616260c2c97d888d3f2decb82a7325bbabf06c840021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a424f3db92efc4b6be0d6beeb40b2cb810776d5f7e066305edd3b3e984497c92 0.600000000000 1866274 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": 1378189, "vin": [ { "gen": { "height": 1378179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a424f3db92efc4b6be0d6beeb40b2cb810776d5f7e066305edd3b3e984497c92" } } ], "extra": [ 1, 146, 115, 45, 232, 31, 58, 54, 234, 139, 103, 93, 230, 22, 38, 12, 44, 151, 216, 136, 211, 242, 222, 203, 130, 167, 50, 91, 186, 191, 6, 200, 64, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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