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: a3fd6c4d22cce04b79029f10c6e0322dbd8f152c62287eab4feed83e4e20da87
Tx prefix hash: ec9c935284e2031748d408c78295fa366089f61a8c6df25b76c8833f8ecdd7ce
Tx public key: a843216d027240f26b71ea0f1ecb73d9284d8106a46a1ac4c2148389d6e68d6d
| Timestamp: 1780998082 | Timestamp [UTC]: 2026-06-09 09:41:22 | Age [y:d:h:m:s]: 00:000:06:18:22 |
| Block: 8388 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 303 | RingCT/type: yes/0 |
| Extra: 01a843216d027240f26b71ea0f1ecb73d9284d8106a46a1ac4c2148389d6e68d6d020900000002e49593ff00 | ||
1 output(s) for total of 34.640677481850 HMNY
| stealth address | amount | amount idx | tag |
| 00: 205d5408e1633075ce263291442063b50b23777f7752f49e8890f250d3c5eb74 | 34.640677481850 | 10368 of 0 | <41> |
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": 8448,
"vin": [ {
"gen": {
"height": 8388
}
}
],
"vout": [ {
"amount": 34640677481850,
"target": {
"tagged_key": {
"key": "205d5408e1633075ce263291442063b50b23777f7752f49e8890f250d3c5eb74",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 168, 67, 33, 109, 2, 114, 64, 242, 107, 113, 234, 15, 30, 203, 115, 217, 40, 77, 129, 6, 164, 106, 26, 196, 194, 20, 131, 137, 214, 230, 141, 109, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}