Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578e3f527367de770622203d44e00a7b31e0c991d5324ec92c10cd623e0ab48e

Tx prefix hash: ac5e70d373803c5278417216647da1f54860d80a6b1685e62199f431bfd29fe8
Tx public key: 1f0e0f1146e5e8219b250f377f649c78a648a85f796e86475950a0cdbfcd67e3
Timestamp: 1787239880 Timestamp [UTC]: 2026-08-20 15:31:20 Age [y:d:h:m:s]: 00:089:06:31:03
Block: 1617564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 63115 RingCT/type: yes/0
Extra: 011f0e0f1146e5e8219b250f377f649c78a648a85f796e86475950a0cdbfcd67e30208ee4ce4fcbed3dc83

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aef79e2bdd91032fef3203f6da0a07e3d795a7acd8449101d7525d5fc982ddee 0.000600000000 2107584 of 15 <97>

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": 1617574, "vin": [ { "gen": { "height": 1617564 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "aef79e2bdd91032fef3203f6da0a07e3d795a7acd8449101d7525d5fc982ddee", "view_tag": "97" } } } ], "extra": [ 1, 31, 14, 15, 17, 70, 229, 232, 33, 155, 37, 15, 55, 127, 100, 156, 120, 166, 72, 168, 95, 121, 110, 134, 71, 89, 80, 160, 205, 191, 205, 103, 227, 2, 8, 238, 76, 228, 252, 190, 211, 220, 131 ], "rct_signatures": { "type": 0 } }


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