Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0652acf688c77b37c505b5f9149c1cac69948fe5058f2399d100149deede82

Tx prefix hash: 29f61f02aea161d7843ad19f9e8d78d25e813d487536c5959aa5982429eefb79
Tx public key: 0f0f18999c01b6e00d57effa0401add872f100e4043df76d92cee26bc87a6107
Timestamp: 1737573664 Timestamp [UCT]: 2025-01-22 19:21:04 Age [y:d:h:m:s]: 00:147:13:36:58
Block: 1203051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105192 RingCT/type: yes/0
Extra: 010f0f18999c01b6e00d57effa0401add872f100e4043df76d92cee26bc87a6107021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f2091d1a7ff10bdd2dbf8fdf900c628d3d362fc4d4f448079aafdf351f1c65b 0.600000000000 1689724 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": 1203061, "vin": [ { "gen": { "height": 1203051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f2091d1a7ff10bdd2dbf8fdf900c628d3d362fc4d4f448079aafdf351f1c65b" } } ], "extra": [ 1, 15, 15, 24, 153, 156, 1, 182, 224, 13, 87, 239, 250, 4, 1, 173, 216, 114, 241, 0, 228, 4, 61, 247, 109, 146, 206, 226, 107, 200, 122, 97, 7, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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