Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390e76fe7d66b161162a25437dacbfe4644eb34fc76d39cd3fdc960b635bda96

Tx prefix hash: 96aeda612ff219792ae704f59356feb3ded6eaee74b4f22b2ec403977e17cfe2
Tx public key: 71c43f91c44d043f61dba222fdc228203351c74b1e7f42f9f109ca5d02e2068b
Timestamp: 1746205690 Timestamp [UTC]: 2025-05-02 17:08:10 Age [y:d:h:m:s]: 01:196:22:21:00
Block: 1274289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404700 RingCT/type: yes/0
Extra: 0171c43f91c44d043f61dba222fdc228203351c74b1e7f42f9f109ca5d02e2068b02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4f70d17f6f7f7b61e0e0f42b39cf3abbfcf0212ed00591186c8be348e0cc745 0.000600000000 1761584 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": 1274299, "vin": [ { "gen": { "height": 1274289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f70d17f6f7f7b61e0e0f42b39cf3abbfcf0212ed00591186c8be348e0cc745" } } ], "extra": [ 1, 113, 196, 63, 145, 196, 77, 4, 63, 97, 219, 162, 34, 253, 194, 40, 32, 51, 81, 199, 75, 30, 127, 66, 249, 241, 9, 202, 93, 2, 226, 6, 139, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: