Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ada680cdc57c42baf56338d9f63b5e351073e87c72fa1275ffd8039bd3b0f8f

Tx prefix hash: b557106fb48240bef4c9265d982e6a76b71c386d9d6f57fe292dd7df93fc13b8
Tx public key: c0500635fefd99aa8609a47ec0a4f39f9177b390d129e865895c7f1dad2efaea
Timestamp: 1718873584 Timestamp [UCT]: 2024-06-20 08:53:04 Age [y:d:h:m:s]: 00:329:07:34:01
Block: 1048215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235354 RingCT/type: yes/0
Extra: 01c0500635fefd99aa8609a47ec0a4f39f9177b390d129e865895c7f1dad2efaea0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 672367422e6595bfc3c0c1576be2943bac089814e2c7db30ec7f71755a2935f7 0.600000000000 1518244 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": 1048225, "vin": [ { "gen": { "height": 1048215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "672367422e6595bfc3c0c1576be2943bac089814e2c7db30ec7f71755a2935f7" } } ], "extra": [ 1, 192, 80, 6, 53, 254, 253, 153, 170, 134, 9, 164, 126, 192, 164, 243, 159, 145, 119, 179, 144, 209, 41, 232, 101, 137, 92, 127, 29, 173, 46, 250, 234, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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