Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cb521810d2fe9c6fdcf6d8f5d101ef6afd52027c275c40f861ed6d6cb9e6f3e

Tx prefix hash: ea03aa0e69e77e41867ee27942cbaaa0bc3edf361a1af3a13d446bf9ed7703fa
Tx public key: ebbd5342c5e4c6c33df723df1bd8132cf8cab69b048a06cb0b2e1bd615ae893d
Timestamp: 1781271072 Timestamp [UTC]: 2026-06-12 13:31:12 Age [y:d:h:m:s]: 00:161:08:06:52
Block: 1557527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 125427 RingCT/type: yes/0
Extra: 01ebbd5342c5e4c6c33df723df1bd8132cf8cab69b048a06cb0b2e1bd615ae893d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3545fbc7246f11f22ab2716f118f2befce0c4e156b46ff5bca9741c4bada2039 0.000600000000 2047505 of 15 <c4>

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": 1557537, "vin": [ { "gen": { "height": 1557527 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3545fbc7246f11f22ab2716f118f2befce0c4e156b46ff5bca9741c4bada2039", "view_tag": "c4" } } } ], "extra": [ 1, 235, 189, 83, 66, 197, 228, 198, 195, 61, 247, 35, 223, 27, 216, 19, 44, 248, 202, 182, 155, 4, 138, 6, 203, 11, 46, 27, 214, 21, 174, 137, 61 ], "rct_signatures": { "type": 0 } }


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