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: 2d3b3974fcb300c3b8f93271e47e8ee53346a2ffeb89a432c8d4752cd99af982
Tx prefix hash: 8a1912258d2ae38f6614de974632348490fb34e4df6448d40aabacdde117c06a
Tx public key: 09c41455c431c067b60f00512ecc8b52f2e3a644132db3ca7d4d2232baf85698
| Timestamp: 1780006581 | Timestamp [UTC]: 2026-05-28 22:16:21 | Age [y:d:h:m:s]: 00:011:00:08:28 |
| Block: 4078 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3808 | RingCT/type: yes/0 |
| Extra: 0109c41455c431c067b60f00512ecc8b52f2e3a644132db3ca7d4d2232baf8569802090000000426697be300 | ||
1 output(s) for total of 34.911830042847 HMNY
| stealth address | amount | amount idx | tag |
| 00: d301d9cc0e7645e10517d554a0960d654d823b31c547dc42d59d0440cd26f8e3 | 34.911830042847 | 5064 of 0 | <ed> |
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": 4138,
"vin": [ {
"gen": {
"height": 4078
}
}
],
"vout": [ {
"amount": 34911830042847,
"target": {
"tagged_key": {
"key": "d301d9cc0e7645e10517d554a0960d654d823b31c547dc42d59d0440cd26f8e3",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 9, 196, 20, 85, 196, 49, 192, 103, 182, 15, 0, 81, 46, 204, 139, 82, 242, 227, 166, 68, 19, 45, 179, 202, 125, 77, 34, 50, 186, 248, 86, 152, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}