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: 6342cc632c0ed36d305dde5bd99d4a235ebe6126885b105b230683f0566f5b3e
Tx prefix hash: 4f16ee8c80bf189f4ce984b1183f473569e5ef6c31c9ff58174f0e792bb1b34e
Tx public key: 39f8331f1022b2deda0f765e8e95c87261461a63cd2ea4de94f3fba61ab90dcf
| Timestamp: 1780716887 | Timestamp [UTC]: 2026-06-06 03:34:47 | Age [y:d:h:m:s]: 00:003:02:03:52 |
| Block: 6205 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1929 | RingCT/type: yes/0 |
| Extra: 0139f8331f1022b2deda0f765e8e95c87261461a63cd2ea4de94f3fba61ab90dcf020900000001e49593ff00 | ||
1 output(s) for total of 34.770481952029 HMNY
| stealth address | amount | amount idx | tag |
| 00: 974af5a273f871e40d8457681c6725333e80b3b2c752c95794e9d534dd5d72b5 | 34.770481952029 | 7684 of 0 | <4c> |
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": 6265,
"vin": [ {
"gen": {
"height": 6205
}
}
],
"vout": [ {
"amount": 34770481952029,
"target": {
"tagged_key": {
"key": "974af5a273f871e40d8457681c6725333e80b3b2c752c95794e9d534dd5d72b5",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 57, 248, 51, 31, 16, 34, 178, 222, 218, 15, 118, 94, 142, 149, 200, 114, 97, 70, 26, 99, 205, 46, 164, 222, 148, 243, 251, 166, 26, 185, 13, 207, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}