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: 0f952e6fea99812d2675aed8c2cb3946a380719e7a3d2761e9f911479fe96e49
Tx prefix hash: 45e5ba801a9defc5481d8f798c9a9d4da6c7dc5679b59b499908d012dd6c9ed7
Tx public key: d4a90facd209225d32974bd63e5922eb7c1d07c5ba1c642ecef83b8b9d3ce3d8
| Timestamp: 1780979010 | Timestamp [UTC]: 2026-06-09 04:23:30 | Age [y:d:h:m:s]: 00:000:08:14:15 |
| Block: 7994 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 584 | RingCT/type: yes/0 |
| Extra: 01d4a90facd209225d32974bd63e5922eb7c1d07c5ba1c642ecef83b8b9d3ce3d8020900000001e49593ff00 | ||
1 output(s) for total of 34.652038570575 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec9c8364e740125470c44a349cc5ce724c9dff9cc36c5903456a6562983a272c | 34.652038570575 | 9912 of 0 | <82> |
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": 8054,
"vin": [ {
"gen": {
"height": 7994
}
}
],
"vout": [ {
"amount": 34652038570575,
"target": {
"tagged_key": {
"key": "ec9c8364e740125470c44a349cc5ce724c9dff9cc36c5903456a6562983a272c",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 212, 169, 15, 172, 210, 9, 34, 93, 50, 151, 75, 214, 62, 89, 34, 235, 124, 29, 7, 197, 186, 28, 100, 46, 206, 248, 59, 139, 157, 60, 227, 216, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}