Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b310202cf39168038fb5e1d072f3e86671047c2b6fd371f957f7ada85bbe4a9e

Tx prefix hash: 117665511ae1d8d140a94dbb7500a308dc3685267a3f78b49ace9f99a6e09184
Tx public key: 14dda2bac9b8a10bdfe9ee2a0d229907da3991e4ce1ff22b98c2709f7e4d7a00
Timestamp: 1735583086 Timestamp [UCT]: 2024-12-30 18:24:46 Age [y:d:h:m:s]: 00:106:18:58:53
Block: 1186611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76127 RingCT/type: yes/0
Extra: 0114dda2bac9b8a10bdfe9ee2a0d229907da3991e4ce1ff22b98c2709f7e4d7a00021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b426242992f56bbf2799075e8caf6ee4c54a659c834a3628b867e3e46c307c 0.600000000000 1673094 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": 1186621, "vin": [ { "gen": { "height": 1186611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b426242992f56bbf2799075e8caf6ee4c54a659c834a3628b867e3e46c307c" } } ], "extra": [ 1, 20, 221, 162, 186, 201, 184, 161, 11, 223, 233, 238, 42, 13, 34, 153, 7, 218, 57, 145, 228, 206, 31, 242, 43, 152, 194, 112, 159, 126, 77, 122, 0, 2, 17, 0, 0, 0, 5, 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