Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2dc1c69bb8c09c29345a50a369f21cf3bba9fb4e5cbafa2e58f8787aa515802

Tx prefix hash: 804c34776bb2d99ebfd26aa16eefe903b7d331264384b7958780c491e0a5a1c4
Tx public key: 8be935c728f151afcb994660f5575316d5f322e7bb6e95e68ef551a46558d0ca
Timestamp: 1783948272 Timestamp [UTC]: 2026-07-13 13:11:12 Age [y:d:h:m:s]: 00:128:07:54:11
Block: 1581370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 100014 RingCT/type: yes/0
Extra: 018be935c728f151afcb994660f5575316d5f322e7bb6e95e68ef551a46558d0ca02087ee7f0303f06c352

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f193a61296a2e9f077b9606d62408d277f2f45e174418fd8bd752d9470406492 0.000600000000 2071362 of 15 <18>

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": 1581380, "vin": [ { "gen": { "height": 1581370 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f193a61296a2e9f077b9606d62408d277f2f45e174418fd8bd752d9470406492", "view_tag": "18" } } } ], "extra": [ 1, 139, 233, 53, 199, 40, 241, 81, 175, 203, 153, 70, 96, 245, 87, 83, 22, 213, 243, 34, 231, 187, 110, 149, 230, 142, 245, 81, 164, 101, 88, 208, 202, 2, 8, 126, 231, 240, 48, 63, 6, 195, 82 ], "rct_signatures": { "type": 0 } }


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