For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 36306d81565381ef59dca41028ff33c6e972bb243c5ab8b0fb99e8d426c31fa9
Tx prefix hash: 38e6dad2f06720a6d658d1beb78e6ef2c87b4779af615ef250104528ff7252ad
Tx public key: 86e069e738d2872fcfbe0c99d4ea22e35e4519faf13a41958934d4107aef852e
| Timestamp: 1780845637 | Timestamp [UTC]: 2026-06-07 15:20:37 | Age [y:d:h:m:s]: 00:001:10:15:20 |
| Block: 7503 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 383 | RingCT/type: yes/0 |
| Extra: 0186e069e738d2872fcfbe0c99d4ea22e35e4519faf13a41958934d4107aef852e020900000001e49593ff00 | ||
1 output(s) for total of 34.687128919571 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7860715fbf92a09c388a82cc71393acdb6134ad89d1ef9fb9d6d3a7267d44f8d | 34.687128919571 | 9247 of 0 | <05> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 7563,
"vin": [ {
"gen": {
"height": 7503
}
}
],
"vout": [ {
"amount": 34687128919571,
"target": {
"tagged_key": {
"key": "7860715fbf92a09c388a82cc71393acdb6134ad89d1ef9fb9d6d3a7267d44f8d",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 134, 224, 105, 231, 56, 210, 135, 47, 207, 190, 12, 153, 212, 234, 34, 227, 94, 69, 25, 250, 241, 58, 65, 149, 137, 52, 212, 16, 122, 239, 133, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}