Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ebe42b5992a6a57ef1a019f4cf0da22f5cd62be5cd7dc36b66369e5dd0aac78

Tx prefix hash: 68451632374692afcabc6aaf17338b04a3390a9da2ec5958f2b47f19278fcd90
Tx public key: bcd4f48ac4fb5f77754e91cc9661a613364e710a9afcc0451e7850880d2f8380
Timestamp: 1772043815 Timestamp [UTC]: 2026-02-25 18:23:35 Age [y:d:h:m:s]: 00:267:19:21:44
Block: 1485698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197035 RingCT/type: yes/0
Extra: 01bcd4f48ac4fb5f77754e91cc9661a613364e710a9afcc0451e7850880d2f8380021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67ecc0709f81c1d097e0338666a31dc9c545450bdaeedbd1d25d8260fa678c3f 0.000600000000 1975136 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": 1485708, "vin": [ { "gen": { "height": 1485698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67ecc0709f81c1d097e0338666a31dc9c545450bdaeedbd1d25d8260fa678c3f" } } ], "extra": [ 1, 188, 212, 244, 138, 196, 251, 95, 119, 117, 78, 145, 204, 150, 97, 166, 19, 54, 78, 113, 10, 154, 252, 192, 69, 30, 120, 80, 136, 13, 47, 131, 128, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 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: