Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c8f6fe1bed41a5bbe5fc298189a7c3b82bdd3b24172627450a0aed3e93c602

Tx prefix hash: e0721ade6e3935a9d09ee3cc2fcaedacae6a610a6f96b3a7d5b6654e48ea852b
Tx public key: 0926c2fbfd8f143bd73fe88aab887883964d93ddff218eb0118e90eab2de0db2
Timestamp: 1579015357 Timestamp [UCT]: 2020-01-14 15:22:37 Age [y:d:h:m:s]: 05:094:12:02:23
Block: 45385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217766 RingCT/type: yes/0
Extra: 010926c2fbfd8f143bd73fe88aab887883964d93ddff218eb0118e90eab2de0db2021100000065b221b3d1000000000000000000

1 output(s) for total of 434.131695653000 dcy

stealth address amount amount idx
00: 80ec90b17ebc28b371acad68ba4f4a313306c94730fc46937d1484474a10b3c6 434.131695653000 82909 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": 45395, "vin": [ { "gen": { "height": 45385 } } ], "vout": [ { "amount": 434131695653, "target": { "key": "80ec90b17ebc28b371acad68ba4f4a313306c94730fc46937d1484474a10b3c6" } } ], "extra": [ 1, 9, 38, 194, 251, 253, 143, 20, 59, 215, 63, 232, 138, 171, 136, 120, 131, 150, 77, 147, 221, 255, 33, 142, 176, 17, 142, 144, 234, 178, 222, 13, 178, 2, 17, 0, 0, 0, 101, 178, 33, 179, 209, 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