Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03376f0aadcf3c3fe832a65c204aba6b9c6c56ab817229a0021bc060240b79c

Tx prefix hash: 9219f0aac5203b0b497c3ec1254bb01d7e9a6d201371408d7fa92d6668cd66ef
Tx public key: d105656f2b07aae0e7d312c5d0ec1dd68779a704643fbaf9f17cf06e4c79cdd0
Timestamp: 1706167796 Timestamp [UCT]: 2024-01-25 07:29:56 Age [y:d:h:m:s]: 01:031:16:17:02
Block: 942849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283701 RingCT/type: yes/0
Extra: 01d105656f2b07aae0e7d312c5d0ec1dd68779a704643fbaf9f17cf06e4c79cdd002110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69629cdee543e0bf1eebb15edf068bb8d8bd8bf08aeea4938627b236274330a4 0.600000000000 1401029 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": 942859, "vin": [ { "gen": { "height": 942849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69629cdee543e0bf1eebb15edf068bb8d8bd8bf08aeea4938627b236274330a4" } } ], "extra": [ 1, 209, 5, 101, 111, 43, 7, 170, 224, 231, 211, 18, 197, 208, 236, 29, 214, 135, 121, 167, 4, 100, 63, 186, 249, 241, 124, 240, 110, 76, 121, 205, 208, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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