Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bccc8f89d5211b1f5393a2e2e9ad79325f61e5dac4226669eba465e2ae3f261e

Tx prefix hash: 50d28a88e50750d478ba1bbdf658eb4c921736380eb63709f87d811866c0a4ab
Tx public key: ce06f3e6ae4ef2ec066ea736e508816a3e16742c24508108b17ab191a4096e27
Timestamp: 1752102035 Timestamp [UCT]: 2025-07-09 23:00:35 Age [y:d:h:m:s]: 00:201:22:21:03
Block: 1322234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142782 RingCT/type: yes/0
Extra: 01ce06f3e6ae4ef2ec066ea736e508816a3e16742c24508108b17ab191a4096e27021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33d3f57af81f83d7c717d073b3495ab47bd6132389d599405cfe2809a893cb0e 0.600000000000 1809961 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": 1322244, "vin": [ { "gen": { "height": 1322234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33d3f57af81f83d7c717d073b3495ab47bd6132389d599405cfe2809a893cb0e" } } ], "extra": [ 1, 206, 6, 243, 230, 174, 78, 242, 236, 6, 110, 167, 54, 229, 8, 129, 106, 62, 22, 116, 44, 36, 80, 129, 8, 177, 122, 177, 145, 164, 9, 110, 39, 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