Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04fef8d4ab490e53d4aa325e813f0b70907335ac46a60614568eec9a472b54ff

Tx prefix hash: c02b0348f8ea46cc08e27e06ce8926c7e62799efaee58aa0dfea82912d910554
Tx public key: 2532536a2e0f60e4b7ec3004cde9a386c27791fd6eabc8dcb0286b48be325425
Timestamp: 1772030977 Timestamp [UTC]: 2026-02-25 14:49:37 Age [y:d:h:m:s]: 00:267:20:43:52
Block: 1485599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197057 RingCT/type: yes/0
Extra: 012532536a2e0f60e4b7ec3004cde9a386c27791fd6eabc8dcb0286b48be32542502110000000df188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 86e5ec0c23c2ca6c680d3371be56a9b1890b99c2844bbf34e965e48fde3055ff 0.000600000000 1975037 of 15 -

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": 1485609, "vin": [ { "gen": { "height": 1485599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86e5ec0c23c2ca6c680d3371be56a9b1890b99c2844bbf34e965e48fde3055ff" } } ], "extra": [ 1, 37, 50, 83, 106, 46, 15, 96, 228, 183, 236, 48, 4, 205, 233, 163, 134, 194, 119, 145, 253, 110, 171, 200, 220, 176, 40, 107, 72, 190, 50, 84, 37, 2, 17, 0, 0, 0, 13, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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