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: ed78d8a339b4f25e04a746898b3681889936be5a7c2be0f72ab6930dbbc0080b
Tx prefix hash: 7fdd489bf6aadd2556373a20453fc018b5dfc4f5c9fa2c361106d4332b4934b2
Tx public key: 1e11d4ff544eb3742b47e06c2128b06e34f13520f6f54216284045a190095c41
| Timestamp: 1780682653 | Timestamp [UTC]: 2026-06-05 18:04:13 | Age [y:d:h:m:s]: 00:003:07:31:44 |
| Block: 5305 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2581 | RingCT/type: yes/0 |
| Extra: 011e11d4ff544eb3742b47e06c2128b06e34f13520f6f54216284045a190095c41020900000001e49593ff00 | ||
1 output(s) for total of 34.830220756650 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1421a8a2d04d3ea7b30dd5d084b159583b10c1860a8a1c1161ff984b51d5c0e9 | 34.830220756650 | 6732 of 0 | <f2> |
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": 5365,
"vin": [ {
"gen": {
"height": 5305
}
}
],
"vout": [ {
"amount": 34830220756650,
"target": {
"tagged_key": {
"key": "1421a8a2d04d3ea7b30dd5d084b159583b10c1860a8a1c1161ff984b51d5c0e9",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 30, 17, 212, 255, 84, 78, 179, 116, 43, 71, 224, 108, 33, 40, 176, 110, 52, 241, 53, 32, 246, 245, 66, 22, 40, 64, 69, 161, 144, 9, 92, 65, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}