Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cee3cac4544c29f693e3528f9d3b2940b4ff080f88cb8946b30dceb6fd7683e

Tx prefix hash: c964d1008abfd32eed4a379f69eded5d63ac801fa38e62c4d7b332462192454c
Tx public key: 84ff8db142cb25dda14536dffd1d2be056b7140ffa493f809d56a03305b4da87
Timestamp: 1724475530 Timestamp [UCT]: 2024-08-24 04:58:50 Age [y:d:h:m:s]: 01:071:19:52:55
Block: 1094666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309770 RingCT/type: yes/0
Extra: 0184ff8db142cb25dda14536dffd1d2be056b7140ffa493f809d56a03305b4da87021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df55e5178df583698ecbfb1acfd0ed76d5afc7e458c95369d1fbd100a9f5d4f1 0.600000000000 1569785 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": 1094676, "vin": [ { "gen": { "height": 1094666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df55e5178df583698ecbfb1acfd0ed76d5afc7e458c95369d1fbd100a9f5d4f1" } } ], "extra": [ 1, 132, 255, 141, 177, 66, 203, 37, 221, 161, 69, 54, 223, 253, 29, 43, 224, 86, 183, 20, 15, 250, 73, 63, 128, 157, 86, 160, 51, 5, 180, 218, 135, 2, 17, 0, 0, 0, 1, 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