Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28cb84223b2d502296706691096d8d8a4875da17089401dce75877582e75361f

Tx prefix hash: 738460b4542ec60dbd69aa097a69310767dca485be5d9c3b71af4e828456326b
Tx public key: 69d7fe8503d643b135cc0125cbe9f8974857c82509398c2fa1e4108dc3f7da0d
Timestamp: 1713110498 Timestamp [UTC]: 2024-04-14 16:01:38 Age [y:d:h:m:s]: 02:221:07:51:45
Block: 1000418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683076 RingCT/type: yes/0
Extra: 0169d7fe8503d643b135cc0125cbe9f8974857c82509398c2fa1e4108dc3f7da0d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de9398891b8bd180eb9958acdbb08393443bc83fb75d5e0ab0c6e8fe9cc8bf40 0.000600000000 1460916 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": 1000428, "vin": [ { "gen": { "height": 1000418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9398891b8bd180eb9958acdbb08393443bc83fb75d5e0ab0c6e8fe9cc8bf40" } } ], "extra": [ 1, 105, 215, 254, 133, 3, 214, 67, 177, 53, 204, 1, 37, 203, 233, 248, 151, 72, 87, 200, 37, 9, 57, 140, 47, 161, 228, 16, 141, 195, 247, 218, 13, 2, 17, 0, 0, 0, 2, 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: