Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7130a9b13a89c62e33088203251e02336dd932deea51b908b72aba8e9981d9

Tx prefix hash: e0bbf623b13a9d3ae9e75ea0a1b7dd4fb94d56c9066be8211cf8cfd1db6bb227
Tx public key: fdce1c4b9d08e68a2399ed699d51e375efa23b5832d364fc72e1f10dd5df0f4a
Timestamp: 1748674435 Timestamp [UCT]: 2025-05-31 06:53:55 Age [y:d:h:m:s]: 00:168:21:37:10
Block: 1294741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118398 RingCT/type: yes/0
Extra: 01fdce1c4b9d08e68a2399ed699d51e375efa23b5832d364fc72e1f10dd5df0f4a021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d20c0b82b2e1dcbf404e48ecf97ba43725108c7afe9037f0bdcdd10d28531b69 0.600000000000 1782238 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": 1294751, "vin": [ { "gen": { "height": 1294741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d20c0b82b2e1dcbf404e48ecf97ba43725108c7afe9037f0bdcdd10d28531b69" } } ], "extra": [ 1, 253, 206, 28, 75, 157, 8, 230, 138, 35, 153, 237, 105, 157, 81, 227, 117, 239, 162, 59, 88, 50, 211, 100, 252, 114, 225, 241, 13, 213, 223, 15, 74, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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