Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43ed9e804f1c3ac1027b1b3354a4e11e25c3766cfeee335cd838daf7e19a31e

Tx prefix hash: b75856a9eb6fdecef14f60218904e72f2e9cad34a909fafd54f145b6fca6e890
Tx public key: 2cb55ca69f0fb66d8de83b21b53bdfb00ec1df3ee68b1d296e822b4cab2224e4
Timestamp: 1734219614 Timestamp [UTC]: 2024-12-14 23:40:14 Age [y:d:h:m:s]: 01:337:01:31:08
Block: 1175354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504690 RingCT/type: yes/0
Extra: 012cb55ca69f0fb66d8de83b21b53bdfb00ec1df3ee68b1d296e822b4cab2224e40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8970250ea2b592a6444954cc12edef50b26eb462f1c8cba09dce02c92fb598d6 0.000600000000 1661625 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": 1175364, "vin": [ { "gen": { "height": 1175354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8970250ea2b592a6444954cc12edef50b26eb462f1c8cba09dce02c92fb598d6" } } ], "extra": [ 1, 44, 181, 92, 166, 159, 15, 182, 109, 141, 232, 59, 33, 181, 59, 223, 176, 14, 193, 223, 62, 230, 139, 29, 41, 110, 130, 43, 76, 171, 34, 36, 228, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: