Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe1dead33d4b082a87b37cfbcfe779c126e29f59453ced418d9ff6660c27fa7

Tx prefix hash: 0ee215cf5b6b9d4b048c2b8272b4c0a8da03bcf690f0b54b412fc2ef9265bbe3
Tx public key: 408eabc046f779d1e4286aefc1b8919a382f7ac5126c96b837d69b37357d88c3
Timestamp: 1747938189 Timestamp [UCT]: 2025-05-22 18:23:09 Age [y:d:h:m:s]: 00:244:21:37:00
Block: 1288648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172661 RingCT/type: yes/0
Extra: 01408eabc046f779d1e4286aefc1b8919a382f7ac5126c96b837d69b37357d88c302110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d00d1cea9dbfcf292cf1647653cb58670e4ccd18dcebd97adb78926be7750cf8 0.600000000000 1776115 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": 1288658, "vin": [ { "gen": { "height": 1288648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d00d1cea9dbfcf292cf1647653cb58670e4ccd18dcebd97adb78926be7750cf8" } } ], "extra": [ 1, 64, 142, 171, 192, 70, 247, 121, 209, 228, 40, 106, 239, 193, 184, 145, 154, 56, 47, 122, 197, 18, 108, 150, 184, 55, 214, 155, 55, 53, 125, 136, 195, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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