Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94222fc36e3e0f878ce3a4c969794c8736bcfe48bb65038b9b275609208cd15e

Tx prefix hash: 4b253f8a725505bce59936480b84e44cf3ddf861368321f5e71bbb942c5667c9
Tx public key: 4d6116e573e8d22d56716a5d874126af49ead8a53a74d31e71fd79bbebdc76d5
Timestamp: 1676536701 Timestamp [UCT]: 2023-02-16 08:38:21 Age [y:d:h:m:s]: 01:330:04:28:43
Block: 698102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496936 RingCT/type: yes/0
Extra: 014d6116e573e8d22d56716a5d874126af49ead8a53a74d31e71fd79bbebdc76d502110000000174b6d784000000000000000000

1 output(s) for total of 2.984682877000 dcy

stealth address amount amount idx
00: 3ba6fb2c4cb6cfe78e2dfda63ac2157a86b20ce1200228023de3264528a0fb6a 2.984682877000 1141375 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": 698112, "vin": [ { "gen": { "height": 698102 } } ], "vout": [ { "amount": 2984682877, "target": { "key": "3ba6fb2c4cb6cfe78e2dfda63ac2157a86b20ce1200228023de3264528a0fb6a" } } ], "extra": [ 1, 77, 97, 22, 229, 115, 232, 210, 45, 86, 113, 106, 93, 135, 65, 38, 175, 73, 234, 216, 165, 58, 116, 211, 30, 113, 253, 121, 187, 235, 220, 118, 213, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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