Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46ef91fac5feb088d0b9f803e620da8aed51a69f643e87c79189b3468be32d3

Tx prefix hash: 127d0c8abf350b327ce8dc78dc04d1967bed7b53f29b96dedd7b4dd6215f73a1
Tx public key: e541a59c6ffd31e36d523e9a4b64c7a9453c035cdf2315dbf116ea3ecbfad3b3
Timestamp: 1790553228 Timestamp [UTC]: 2026-09-27 23:53:48 Age [y:d:h:m:s]: 00:049:00:54:35
Block: 1645055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 34221 RingCT/type: yes/0
Extra: 01e541a59c6ffd31e36d523e9a4b64c7a9453c035cdf2315dbf116ea3ecbfad3b3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa38f4fdfdc7a3720db5cb13f6958d2a90b88d730271067bb5159a69d7140d27 0.000600000000 2135141 of 15 <74>

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": 1645065, "vin": [ { "gen": { "height": 1645055 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "fa38f4fdfdc7a3720db5cb13f6958d2a90b88d730271067bb5159a69d7140d27", "view_tag": "74" } } } ], "extra": [ 1, 229, 65, 165, 156, 111, 253, 49, 227, 109, 82, 62, 154, 75, 100, 199, 169, 69, 60, 3, 92, 223, 35, 21, 219, 241, 22, 234, 62, 203, 250, 211, 179 ], "rct_signatures": { "type": 0 } }


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