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: 37eee989690892f92ba740fc59aa0c88e6684f2f1a5b384ecc1ef567b02ef394
Tx prefix hash: 4021c7608794bf9f16b307f6c2aa9debdfd6b33db1e76fcdbac37bf6762889fd
Tx public key: 7728ae43917dfe187f44f8267e45296e61a47a7d4001deee1eab44d97883ce7d
| Timestamp: 1779954735 | Timestamp [UTC]: 2026-05-28 07:52:15 | Age [y:d:h:m:s]: 00:011:16:54:32 |
| Block: 3674 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4212 | RingCT/type: yes/0 |
| Extra: 017728ae43917dfe187f44f8267e45296e61a47a7d4001deee1eab44d97883ce7d02090000000326697be300 | ||
1 output(s) for total of 34.938742404740 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a28b9611ec42bf07d15e89827d4fc22df15016d8ea8867e104c3e97c9193b99 | 34.938742404740 | 4441 of 0 | <e4> |
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": 3734,
"vin": [ {
"gen": {
"height": 3674
}
}
],
"vout": [ {
"amount": 34938742404740,
"target": {
"tagged_key": {
"key": "7a28b9611ec42bf07d15e89827d4fc22df15016d8ea8867e104c3e97c9193b99",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 119, 40, 174, 67, 145, 125, 254, 24, 127, 68, 248, 38, 126, 69, 41, 110, 97, 164, 122, 125, 64, 1, 222, 238, 30, 171, 68, 217, 120, 131, 206, 125, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}