Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f781a7208a04b4ea40acb7aca23116ad5f3d0bd7ed21437abc1b83073590a7

Tx prefix hash: 53b6f5cb02bf4a8694b61538b293ee6fa495e61c9aac4008a16d12c62719dda1
Tx public key: 19cb7ee13f130851cc8285415a2b245efa22345902b047191278219e0c27a4b5
Timestamp: 1705390706 Timestamp [UCT]: 2024-01-16 07:38:26 Age [y:d:h:m:s]: 01:298:23:33:31
Block: 936408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472517 RingCT/type: yes/0
Extra: 0119cb7ee13f130851cc8285415a2b245efa22345902b047191278219e0c27a4b502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa2b8e3178e80fbcab4ae281d2b8edcd220d5f931a55562ff7f5822542dfa84 0.600000000000 1394434 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": 936418, "vin": [ { "gen": { "height": 936408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa2b8e3178e80fbcab4ae281d2b8edcd220d5f931a55562ff7f5822542dfa84" } } ], "extra": [ 1, 25, 203, 126, 225, 63, 19, 8, 81, 204, 130, 133, 65, 90, 43, 36, 94, 250, 34, 52, 89, 2, 176, 71, 25, 18, 120, 33, 158, 12, 39, 164, 181, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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