Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ac1ea6068da0f1c2f673699866bbfa4dd066e1e3f0ce766cfba0d2276343b3e

Tx prefix hash: 2b9247de0a885f937cd56b9eb1d173947a8ab6ea7c8cc58415645339ed8300bb
Tx public key: bd066487763ce45b35d96aa520dadba1c20df2391d08093328abc12da985bfb5
Timestamp: 1783843321 Timestamp [UTC]: 2026-07-12 08:02:01 Age [y:d:h:m:s]: 00:133:13:26:06
Block: 1580453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 103697 RingCT/type: yes/0
Extra: 01bd066487763ce45b35d96aa520dadba1c20df2391d08093328abc12da985bfb50208037edeaf5842c439

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e1c676933a3c29b91522e1f8106f916ff1162911adf1cb5c0355817a498ac1b 0.000600000000 2070445 of 15 <7e>

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": 1580463, "vin": [ { "gen": { "height": 1580453 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "8e1c676933a3c29b91522e1f8106f916ff1162911adf1cb5c0355817a498ac1b", "view_tag": "7e" } } } ], "extra": [ 1, 189, 6, 100, 135, 118, 60, 228, 91, 53, 217, 106, 165, 32, 218, 219, 161, 194, 13, 242, 57, 29, 8, 9, 51, 40, 171, 193, 45, 169, 133, 191, 181, 2, 8, 3, 126, 222, 175, 88, 66, 196, 57 ], "rct_signatures": { "type": 0 } }


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