Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff35c8ca81fc996ad21b4cd092612253bce8918e5acde1e9d56ea48b11e0a8a7

Tx prefix hash: 4190c593735a571f947275899ea0df8dcc0a798a6cdcbb63dd16265abd185901
Tx public key: f9ab289dfb812a877b3dccf647e3b43e5b48ad3c30c9ac68d7745314c323ad40
Timestamp: 1708926043 Timestamp [UTC]: 2024-02-26 05:40:43 Age [y:d:h:m:s]: 02:265:16:08:20
Block: 965754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714915 RingCT/type: yes/0
Extra: 01f9ab289dfb812a877b3dccf647e3b43e5b48ad3c30c9ac68d7745314c323ad4002110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f84c65f80cbe1f7fddbd7b7e3de3e8de05ea08f4a078e13a0a97171bb7b6ac24 0.000600000000 1425509 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": 965764, "vin": [ { "gen": { "height": 965754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f84c65f80cbe1f7fddbd7b7e3de3e8de05ea08f4a078e13a0a97171bb7b6ac24" } } ], "extra": [ 1, 249, 171, 40, 157, 251, 129, 42, 135, 123, 61, 204, 246, 71, 227, 180, 62, 91, 72, 173, 60, 48, 201, 172, 104, 215, 116, 83, 20, 195, 35, 173, 64, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: