Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a5ab2b0ee0f9b31d4564f5fec74c7dec8bbe98aff1a3f119dc204f8bf2ab88

Tx prefix hash: fd8f8d9915cc8e7bf21022447efe3336ae176395c80e1e9e1a2d5b864b10d4ef
Tx public key: a6f4b1f8807b0e6855b10ac31ca0b807146d689d666f688f589262e7aae96a93
Timestamp: 1761089406 Timestamp [UTC]: 2025-10-21 23:30:06 Age [y:d:h:m:s]: 01:031:04:07:05
Block: 1395090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288404 RingCT/type: yes/0
Extra: 01a6f4b1f8807b0e6855b10ac31ca0b807146d689d666f688f589262e7aae96a9302110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 79e0ea85508e39d7aaea0ba6f19f1d89abe28d92936d91fc3e4fefda22c2ba37 0.000600000000 1883367 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": 1395100, "vin": [ { "gen": { "height": 1395090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79e0ea85508e39d7aaea0ba6f19f1d89abe28d92936d91fc3e4fefda22c2ba37" } } ], "extra": [ 1, 166, 244, 177, 248, 128, 123, 14, 104, 85, 177, 10, 195, 28, 160, 184, 7, 20, 109, 104, 157, 102, 111, 104, 143, 88, 146, 98, 231, 170, 233, 106, 147, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: