Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8fab4380233d02084ea9bcbb3a2f6617b971e565e7dde528116b94c28c8c2b5

Tx prefix hash: 125b71be1e8bd920b4192a433d40e84be72716fa7aaa35acae6bd328027d3c28
Tx public key: 6f3b8f5323843df82fd3b24fc149c3a900b85760adb8711206d11c0f28a298de
Timestamp: 1708922005 Timestamp [UCT]: 2024-02-26 04:33:25 Age [y:d:h:m:s]: 01:282:15:33:16
Block: 965724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460786 RingCT/type: yes/0
Extra: 016f3b8f5323843df82fd3b24fc149c3a900b85760adb8711206d11c0f28a298de0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52fb89cb13933438dbe333d2dc78df4769da33efb5f143e95b83a604883b8a26 0.600000000000 1425479 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": 965734, "vin": [ { "gen": { "height": 965724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52fb89cb13933438dbe333d2dc78df4769da33efb5f143e95b83a604883b8a26" } } ], "extra": [ 1, 111, 59, 143, 83, 35, 132, 61, 248, 47, 211, 178, 79, 193, 73, 195, 169, 0, 184, 87, 96, 173, 184, 113, 18, 6, 209, 28, 15, 40, 162, 152, 222, 2, 17, 0, 0, 0, 6, 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