Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a3fbd5b8be63e4bec0bcaa36ff6de6c7ffcd6f786fe40dfb86292fa943d7bef

Tx prefix hash: 6d412688aa8de2b53f7732fd69b72a7a56316725caa5bee3c48dbf5fefe42248
Tx public key: a96f4ec259ce114785524db9588e0f2d8ac4a604a878d67ec263c4f7e51df001
Timestamp: 1775023767 Timestamp [UTC]: 2026-04-01 06:09:27 Age [y:d:h:m:s]: 00:232:10:36:00
Block: 1510316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171704 RingCT/type: yes/0
Extra: 01a96f4ec259ce114785524db9588e0f2d8ac4a604a878d67ec263c4f7e51df001021100000008e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bbce126da7e589eac78d09f821e543a0d722d2ddd1318eb13a12e331502dc731 0.000600000000 2000098 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 dinastycoin-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": 1510326, "vin": [ { "gen": { "height": 1510316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbce126da7e589eac78d09f821e543a0d722d2ddd1318eb13a12e331502dc731" } } ], "extra": [ 1, 169, 111, 78, 194, 89, 206, 17, 71, 133, 82, 77, 185, 88, 142, 15, 45, 138, 196, 166, 4, 168, 120, 214, 126, 194, 99, 196, 247, 229, 29, 240, 1, 2, 17, 0, 0, 0, 8, 227, 215, 220, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: