Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3a98aa1e725c72038988ad6d73f479b4cea41f35efb689f40089f6e98b7010d

Tx prefix hash: ec6f6870751aab01a15efb17e23033a880b0770a291a6c9a9ac8e8c4e4c7e1c7
Tx public key: 13c80a6afc560cb82381b92f5faa7e050c96652a96ff4c708c89f138ad840b57
Timestamp: 1703110938 Timestamp [UCT]: 2023-12-20 22:22:18 Age [y:d:h:m:s]: 01:326:17:01:05
Block: 917560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492318 RingCT/type: yes/0
Extra: 0113c80a6afc560cb82381b92f5faa7e050c96652a96ff4c708c89f138ad840b57021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4ef1a3b9a6c11d8e5039156f4814e5916c1a2826bc802d5e0a7c340c34bc1b3 0.600000000000 1375142 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": 917570, "vin": [ { "gen": { "height": 917560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4ef1a3b9a6c11d8e5039156f4814e5916c1a2826bc802d5e0a7c340c34bc1b3" } } ], "extra": [ 1, 19, 200, 10, 106, 252, 86, 12, 184, 35, 129, 185, 47, 95, 170, 126, 5, 12, 150, 101, 42, 150, 255, 76, 112, 140, 137, 241, 56, 173, 132, 11, 87, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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