Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950d5aec9ca200aff8279f4dbffce6aa5cb0ba8f3be1e78d819367d6b0a9914c

Tx prefix hash: ada8c16acb1cdf9933b584646cc2e21ed0b4a9df360c3fab865a8ba373db5581
Tx public key: 75a39384ac15206d5c51458620ce81f842abcf11757ba77aae4b773ab4ad8150
Timestamp: 1709413439 Timestamp [UTC]: 2024-03-02 21:03:59 Age [y:d:h:m:s]: 02:257:02:34:50
Block: 969793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708696 RingCT/type: yes/0
Extra: 0175a39384ac15206d5c51458620ce81f842abcf11757ba77aae4b773ab4ad81500211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a12016c8263077be37c54e553e0053f027f2654f326a76bb8aa083ae6e2e1bd 0.000600000000 1429638 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": 969803, "vin": [ { "gen": { "height": 969793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a12016c8263077be37c54e553e0053f027f2654f326a76bb8aa083ae6e2e1bd" } } ], "extra": [ 1, 117, 163, 147, 132, 172, 21, 32, 109, 92, 81, 69, 134, 32, 206, 129, 248, 66, 171, 207, 17, 117, 123, 167, 122, 174, 75, 119, 58, 180, 173, 129, 80, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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: