Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b42f89a0ea79bb00b619d2f05ab7e9b63b82f42519400543f9798881df12fd

Tx prefix hash: 28802a4ee63c7535f8c109ba99fa7921e1ef73edc1c0fb0e0984ce6907dcceef
Tx public key: 3aa1b06e491b4750fedea22ff773c82e9b7ec90d6679a9818fbb29f7d3184399
Timestamp: 1681190761 Timestamp [UCT]: 2023-04-11 05:26:01 Age [y:d:h:m:s]: 02:044:03:36:42
Block: 736050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553749 RingCT/type: yes/0
Extra: 013aa1b06e491b4750fedea22ff773c82e9b7ec90d6679a9818fbb29f7d3184399021100000008b3164c24000000000000000000

1 output(s) for total of 2.234400525000 dcy

stealth address amount amount idx
00: 5af8cbc6ce8817f17dc14981799478b555f18dae34fdba9019299d73e4c21501 2.234400525000 1182439 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": 736060, "vin": [ { "gen": { "height": 736050 } } ], "vout": [ { "amount": 2234400525, "target": { "key": "5af8cbc6ce8817f17dc14981799478b555f18dae34fdba9019299d73e4c21501" } } ], "extra": [ 1, 58, 161, 176, 110, 73, 27, 71, 80, 254, 222, 162, 47, 247, 115, 200, 46, 155, 126, 201, 13, 102, 121, 169, 129, 143, 187, 41, 247, 211, 24, 67, 153, 2, 17, 0, 0, 0, 8, 179, 22, 76, 36, 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