Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f8504fe92fb0ec5be3fa0c7c9d3d43f5057c8f7e2f44b79cb2ed0e88225a480

Tx prefix hash: 565a94a2c02a7047b5074d443cb3cc5fea54f7a94cee0e76d2c4fcbb6c46458a
Tx public key: a3f5f4aa75469a436a5f73e1c740c8aa4dde8082423b8d262dea73bdc32fdd5a
Timestamp: 1788860259 Timestamp [UTC]: 2026-09-08 09:37:39 Age [y:d:h:m:s]: 00:068:04:35:42
Block: 1630814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 48132 RingCT/type: yes/0
Extra: 01a3f5f4aa75469a436a5f73e1c740c8aa4dde8082423b8d262dea73bdc32fdd5a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c6cb5ca1cd4503e9ecbed6d74c7b53ad4b0e0211ac41ef3f848875fc3c922ae 0.000600000000 2120834 of 15 <b4>

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": 1630824, "vin": [ { "gen": { "height": 1630814 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "7c6cb5ca1cd4503e9ecbed6d74c7b53ad4b0e0211ac41ef3f848875fc3c922ae", "view_tag": "b4" } } } ], "extra": [ 1, 163, 245, 244, 170, 117, 70, 154, 67, 106, 95, 115, 225, 199, 64, 200, 170, 77, 222, 128, 130, 66, 59, 141, 38, 45, 234, 115, 189, 195, 47, 221, 90 ], "rct_signatures": { "type": 0 } }


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