Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2163dcb8bb1d04f1ff31afbb9dbb83ee3a27b78c8f7295b0e1f6052463c3b9f3

Tx prefix hash: d0a665b27b6e50b20562eed929393169f44172f96894d9a27ecd454344d5e911
Tx public key: 578ac76aa3091429ca5ff7ec08e456b9ac988bb40e928c0b83fa36d64bf4e18f
Timestamp: 1788179717 Timestamp [UTC]: 2026-08-31 12:35:17 Age [y:d:h:m:s]: 00:081:13:28:30
Block: 1625083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 58012 RingCT/type: yes/0
Extra: 01578ac76aa3091429ca5ff7ec08e456b9ac988bb40e928c0b83fa36d64bf4e18f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1936a8030ee059cd4fe2934677a313a0dfda2f2f2ce1aa6ed60fe137bf0ed9c3 0.000600000000 2115103 of 15 <80>

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": 1625093, "vin": [ { "gen": { "height": 1625083 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1936a8030ee059cd4fe2934677a313a0dfda2f2f2ce1aa6ed60fe137bf0ed9c3", "view_tag": "80" } } } ], "extra": [ 1, 87, 138, 199, 106, 163, 9, 20, 41, 202, 95, 247, 236, 8, 228, 86, 185, 172, 152, 139, 180, 14, 146, 140, 11, 131, 250, 54, 214, 75, 244, 225, 143 ], "rct_signatures": { "type": 0 } }


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