Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d2c88fd53ca37b486f9869f1a9b5c2abe4ac5e98ab6856c86ee71baed3ca4a

Tx prefix hash: 56402c0199476601814b51697480c1387a084518847b1f077897f3e73c321f00
Tx public key: e2a99e68a1d2f6c11d31906c28059bdc87b67f8fee23f0128a3452f608329d50
Timestamp: 1714382184 Timestamp [UCT]: 2024-04-29 09:16:24 Age [y:d:h:m:s]: 00:339:20:57:09
Block: 1010983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242957 RingCT/type: yes/0
Extra: 01e2a99e68a1d2f6c11d31906c28059bdc87b67f8fee23f0128a3452f608329d500211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe559f68e8340103de8641def9fc1bf505ba319e5d61a63219f33138e93a05b 0.600000000000 1473081 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": 1010993, "vin": [ { "gen": { "height": 1010983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe559f68e8340103de8641def9fc1bf505ba319e5d61a63219f33138e93a05b" } } ], "extra": [ 1, 226, 169, 158, 104, 161, 210, 246, 193, 29, 49, 144, 108, 40, 5, 155, 220, 135, 182, 127, 143, 238, 35, 240, 18, 138, 52, 82, 246, 8, 50, 157, 80, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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