Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cfee8cd33e0641a7f7bb5b3d1a613acc1511b014218174527e942d5f7f8e77d

Tx prefix hash: 9b8a146107a296cfefd4daf4df3bcc26f94d034a9bf5ae1d780a110a30b19a5f
Tx public key: 35b7964374491eaac16975f4c0431587c0096a5026a74db92c4e09a7ef619a58
Timestamp: 1725302397 Timestamp [UCT]: 2024-09-02 18:39:57 Age [y:d:h:m:s]: 00:173:12:22:57
Block: 1101513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123812 RingCT/type: yes/0
Extra: 0135b7964374491eaac16975f4c0431587c0096a5026a74db92c4e09a7ef619a58021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da43c71258724d2f6bd3931726d850fd58e887c86944f4fadb218b6c609bad0 0.600000000000 1577592 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": 1101523, "vin": [ { "gen": { "height": 1101513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da43c71258724d2f6bd3931726d850fd58e887c86944f4fadb218b6c609bad0" } } ], "extra": [ 1, 53, 183, 150, 67, 116, 73, 30, 170, 193, 105, 117, 244, 192, 67, 21, 135, 192, 9, 106, 80, 38, 167, 77, 185, 44, 78, 9, 167, 239, 97, 154, 88, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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