Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f2527c4724cc436b52998be6c288ed0fa13675a39e83d2ca58d3f577bf1c5e

Tx prefix hash: b8d2b239000e4a8bfbdbdacc0349a1e636f9dc964964b901b776b20bc43b684e
Tx public key: aab918d9b75aeb9b17c4ae2981e70dd5b817eb4c8079fa7627aabb941e89978f
Timestamp: 1754392943 Timestamp [UCT]: 2025-08-05 11:22:23 Age [y:d:h:m:s]: 00:064:08:22:17
Block: 1340755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44903 RingCT/type: yes/0
Extra: 01aab918d9b75aeb9b17c4ae2981e70dd5b817eb4c8079fa7627aabb941e89978f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a95ef96c0f7d3fe1f41895a5f1ee8352944a4957db3e6b96cb41bbc8d8a79b0f 0.600000000000 1828576 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": 1340765, "vin": [ { "gen": { "height": 1340755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a95ef96c0f7d3fe1f41895a5f1ee8352944a4957db3e6b96cb41bbc8d8a79b0f" } } ], "extra": [ 1, 170, 185, 24, 217, 183, 90, 235, 155, 23, 196, 174, 41, 129, 231, 13, 213, 184, 23, 235, 76, 128, 121, 250, 118, 39, 170, 187, 148, 30, 137, 151, 143, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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