Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af699f35e6361bfb3f4e99392677dd5148bae312534f4121931906a8fcb4a8db

Tx prefix hash: 26681ce4ad214af59ec6cafe23faba0360cf97a3b5c2c609c9aef9e18859ba15
Tx public key: a9d6b46e960a58d4ee246ae8238d99898839efac6d8da3f851400280b6e578f9
Timestamp: 1755033898 Timestamp [UTC]: 2025-08-12 21:24:58 Age [y:d:h:m:s]: 00:271:14:27:32
Block: 1345698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185831 RingCT/type: yes/0
Extra: 01a9d6b46e960a58d4ee246ae8238d99898839efac6d8da3f851400280b6e578f9021100000002d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd20bf282eded12f54d98ea0a89279ba7d7c5ef00cd6d4bf11b1e290b8ccd65d 0.000600000000 1833593 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": 1345708, "vin": [ { "gen": { "height": 1345698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd20bf282eded12f54d98ea0a89279ba7d7c5ef00cd6d4bf11b1e290b8ccd65d" } } ], "extra": [ 1, 169, 214, 180, 110, 150, 10, 88, 212, 238, 36, 106, 232, 35, 141, 153, 137, 136, 57, 239, 172, 109, 141, 163, 248, 81, 64, 2, 128, 182, 229, 120, 249, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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: