Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d4620cb754539b3b98a6743ea580f871a6e487fa79fc7bbdf7f77ebc4628d5b

Tx prefix hash: 6bc0589c2f99ca4a88c19a969c57b5c34bd9d40115376d1b216df1f1706d8e9d
Tx public key: f3ccd1448c84d6248f22d1e5d0c1df7410e4264154050df7009e57f9d7e7c3d2
Timestamp: 1761657368 Timestamp [UTC]: 2025-10-28 13:16:08 Age [y:d:h:m:s]: 01:019:16:18:38
Block: 1399810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280360 RingCT/type: yes/0
Extra: 01f3ccd1448c84d6248f22d1e5d0c1df7410e4264154050df7009e57f9d7e7c3d202110000000525a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0ed9d6ac886615ccd549939f46179d68527ab628038bebdf13129f5868730b81 0.000600000000 1888115 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": 1399820, "vin": [ { "gen": { "height": 1399810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed9d6ac886615ccd549939f46179d68527ab628038bebdf13129f5868730b81" } } ], "extra": [ 1, 243, 204, 209, 68, 140, 132, 214, 36, 143, 34, 209, 229, 208, 193, 223, 116, 16, 228, 38, 65, 84, 5, 13, 247, 0, 158, 87, 249, 215, 231, 195, 210, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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: