Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db70f2744e98c4cc8b674896b37ee724a5eca99d269c8e6fd4175fde2c22a86a

Tx prefix hash: f4fd52d4735a8a05c10be4a99e0ef4228fb20fac4edcb17771a9a6caca383606
Tx public key: 1fa66fec8e6c31c9a5dfc5a28f1c1fdfb979f2408fc7c75cd5d4e9e5d394a2bc
Timestamp: 1785576732 Timestamp [UTC]: 2026-08-01 09:32:12 Age [y:d:h:m:s]: 00:112:11:42:10
Block: 1603470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 80024 RingCT/type: yes/0
Extra: 011fa66fec8e6c31c9a5dfc5a28f1c1fdfb979f2408fc7c75cd5d4e9e5d394a2bc

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b5c170f70f19999789de169db313eaeb5c732a29f0c992330a560e6309152d2 0.000600000000 2093488 of 15 <08>

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": 1603480, "vin": [ { "gen": { "height": 1603470 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4b5c170f70f19999789de169db313eaeb5c732a29f0c992330a560e6309152d2", "view_tag": "08" } } } ], "extra": [ 1, 31, 166, 111, 236, 142, 108, 49, 201, 165, 223, 197, 162, 143, 28, 31, 223, 185, 121, 242, 64, 143, 199, 199, 92, 213, 212, 233, 229, 211, 148, 162, 188 ], "rct_signatures": { "type": 0 } }


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