Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d96f17c29c49291c32343e758b26a75ba1d7b28fbd6cdbc63f84aa90c773f5

Tx prefix hash: 285ca28f77104c1dc8ae69416d9659dc71fc80950d10871d2372146ad57e11cf
Tx public key: 799ac5a19b015c2ce8b6d6ba5dcb698f125ee80d1959f31c0671ecb638702694
Timestamp: 1771963983 Timestamp [UTC]: 2026-02-24 20:13:03 Age [y:d:h:m:s]: 00:268:15:57:29
Block: 1485014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197659 RingCT/type: yes/0
Extra: 01799ac5a19b015c2ce8b6d6ba5dcb698f125ee80d1959f31c0671ecb638702694021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f1ff004c993b242ee89575a8e1d4b2424f7cf7458932809eea2cb4749d739b37 0.000600000000 1974446 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": 1485024, "vin": [ { "gen": { "height": 1485014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ff004c993b242ee89575a8e1d4b2424f7cf7458932809eea2cb4749d739b37" } } ], "extra": [ 1, 121, 154, 197, 161, 155, 1, 92, 44, 232, 182, 214, 186, 93, 203, 105, 143, 18, 94, 232, 13, 25, 89, 243, 28, 6, 113, 236, 182, 56, 112, 38, 148, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: