Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f42bc3dd8850fe6a5d7c4f4cede2b40f2928064a4fd110a2ffc88b51760391f0

Tx prefix hash: cc2b21604ec560f2adbe3b2a08db1469b984c861e3d766f7ba4d6329b97f6e5d
Tx public key: 4462a25ea869e47b127c2494b0bce1eef79ee5d6f966b3e19b830f2b6769ae52
Timestamp: 1787580642 Timestamp [UTC]: 2026-08-24 14:10:42 Age [y:d:h:m:s]: 00:082:12:20:53
Block: 1619999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 58575 RingCT/type: yes/0
Extra: 014462a25ea869e47b127c2494b0bce1eef79ee5d6f966b3e19b830f2b6769ae52

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 008cf4f713687e761d8d0ea507da222e8139a08b4fb832ac0ef1095a8cd35b8a 0.000600000000 2110019 of 15 <2e>

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": 1620009, "vin": [ { "gen": { "height": 1619999 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "008cf4f713687e761d8d0ea507da222e8139a08b4fb832ac0ef1095a8cd35b8a", "view_tag": "2e" } } } ], "extra": [ 1, 68, 98, 162, 94, 168, 105, 228, 123, 18, 124, 36, 148, 176, 188, 225, 238, 247, 158, 229, 214, 249, 102, 179, 225, 155, 131, 15, 43, 103, 105, 174, 82 ], "rct_signatures": { "type": 0 } }


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