Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb6e5b4b0432d230b94caa9201a1e62cac34a2d00c47d1362d83ac1ee1a60a6f

Tx prefix hash: bce4f8724041349c3410a519c1d923bcf563d9be74b047fd362818b3eaf840e8
Tx public key: 5e266bb81ca975e748268844a845e5a72b750ed3a666b59d881ded59d45ce9f2
Timestamp: 1754932738 Timestamp [UCT]: 2025-08-11 17:18:58 Age [y:d:h:m:s]: 00:173:00:49:59
Block: 1344939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122836 RingCT/type: yes/0
Extra: 015e266bb81ca975e748268844a845e5a72b750ed3a666b59d881ded59d45ce9f2021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 600b9e23c897936696a2e9a0c8586a1276bcfc463fe1cc6d93768a95539008fb 0.600000000000 1832826 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": 1344949, "vin": [ { "gen": { "height": 1344939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "600b9e23c897936696a2e9a0c8586a1276bcfc463fe1cc6d93768a95539008fb" } } ], "extra": [ 1, 94, 38, 107, 184, 28, 169, 117, 231, 72, 38, 136, 68, 168, 69, 229, 167, 43, 117, 14, 211, 166, 102, 181, 157, 136, 29, 237, 89, 212, 92, 233, 242, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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