Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d758620ec34111247d926c9c9af4f51a26435b52c0f27fc2da37828d2572ef4

Tx prefix hash: 741735d495d3611706d0d10f7fe2cfec4c18055f3d0437c66524ed1ee912f226
Tx public key: 14f5681428f5857c346d2b756aa214f500b650110f6fd9cffc7db6b4c74bc7f8
Timestamp: 1714595074 Timestamp [UCT]: 2024-05-01 20:24:34 Age [y:d:h:m:s]: 00:363:12:23:27
Block: 1012751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259887 RingCT/type: yes/0
Extra: 0114f5681428f5857c346d2b756aa214f500b650110f6fd9cffc7db6b4c74bc7f80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa0a1eb00de47d9e9185693716a39d7bc625a4763415b1d7c893abb3982f07aa 0.600000000000 1475367 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": 1012761, "vin": [ { "gen": { "height": 1012751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa0a1eb00de47d9e9185693716a39d7bc625a4763415b1d7c893abb3982f07aa" } } ], "extra": [ 1, 20, 245, 104, 20, 40, 245, 133, 124, 52, 109, 43, 117, 106, 162, 20, 245, 0, 182, 80, 17, 15, 111, 217, 207, 252, 125, 182, 180, 199, 75, 199, 248, 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