Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee82df41441a1170e01e7fcb7d12f7f29e2f58565cb9c1878857e60b9811b54

Tx prefix hash: 8b89ef70c04a773fc5f211e3c431497ace3a9b966c400217e3268f2106d839ee
Tx public key: b8ca994083d8b7963f6345b12fc7abf91fdfb736e521a6157425902224bdee61
Timestamp: 1702286265 Timestamp [UCT]: 2023-12-11 09:17:45 Age [y:d:h:m:s]: 01:133:05:59:34
Block: 910700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356377 RingCT/type: yes/0
Extra: 01b8ca994083d8b7963f6345b12fc7abf91fdfb736e521a6157425902224bdee61021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600050000000 dcy

stealth address amount amount idx
00: e0f8feaa14247f6a4757b8d59403ec858d73cd910378c64249ded7817a6ca74f 0.600050000000 1367865 of 0

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": 910710, "vin": [ { "gen": { "height": 910700 } } ], "vout": [ { "amount": 600050000, "target": { "key": "e0f8feaa14247f6a4757b8d59403ec858d73cd910378c64249ded7817a6ca74f" } } ], "extra": [ 1, 184, 202, 153, 64, 131, 216, 183, 150, 63, 99, 69, 177, 47, 199, 171, 249, 31, 223, 183, 54, 229, 33, 166, 21, 116, 37, 144, 34, 36, 189, 238, 97, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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