Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39ef5fc166020e7951966e1ce24a8813ec44af7e8385d3a63cdd7f4a98ba2826

Tx prefix hash: 2dd01e467611631616e97d7b5046cf280762eeb68ace627dae3fd4911bf64a02
Tx public key: e430ef0b372c4e4cf9aa48f664e4deecf3fa9fd4c4fb33030a0cd3ccf950a186
Timestamp: 1708546228 Timestamp [UCT]: 2024-02-21 20:10:28 Age [y:d:h:m:s]: 01:083:05:23:09
Block: 962597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320531 RingCT/type: yes/0
Extra: 01e430ef0b372c4e4cf9aa48f664e4deecf3fa9fd4c4fb33030a0cd3ccf950a18602110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d225b8c5b82f6134a8e576fd75664ccf99a43165ec3a0d44191d1665f2dab4ab 0.600000000000 1422246 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": 962607, "vin": [ { "gen": { "height": 962597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d225b8c5b82f6134a8e576fd75664ccf99a43165ec3a0d44191d1665f2dab4ab" } } ], "extra": [ 1, 228, 48, 239, 11, 55, 44, 78, 76, 249, 170, 72, 246, 100, 228, 222, 236, 243, 250, 159, 212, 196, 251, 51, 3, 10, 12, 211, 204, 249, 80, 161, 134, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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