Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 659dc022779299baca4667d592587e89da8fb004d80fecae835dd42c1cf7b7f0

Tx prefix hash: 4826ecfb882834f41f8765d7227c8fe6a09691b52f027b8c215b6baa9b3d35e0
Tx public key: e0bb082b8d670674f2882ee2e7cc93335f7104090d79c2efa6fbe1c491b1932c
Timestamp: 1752910766 Timestamp [UCT]: 2025-07-19 07:39:26 Age [y:d:h:m:s]: 00:024:11:39:39
Block: 1328685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16953 RingCT/type: yes/0
Extra: 01e0bb082b8d670674f2882ee2e7cc93335f7104090d79c2efa6fbe1c491b1932c021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5759cd254bcf81fdf13839dd10c6dc1099579b7582908ad41163d5d90ff6435a 0.600000000000 1816448 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": 1328695, "vin": [ { "gen": { "height": 1328685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5759cd254bcf81fdf13839dd10c6dc1099579b7582908ad41163d5d90ff6435a" } } ], "extra": [ 1, 224, 187, 8, 43, 141, 103, 6, 116, 242, 136, 46, 226, 231, 204, 147, 51, 95, 113, 4, 9, 13, 121, 194, 239, 166, 251, 225, 196, 145, 177, 147, 44, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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