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: ab1d2968e23819d558ae3892b8f656dc1f2d28fe162d6262833f037982c38f34
Tx prefix hash: 58fc887a663acc0d7537d46a49afefba6c968d81d95a3665796b17276687f36f
Tx public key: 6c021c5dfbf2ff45c550572c21ea9a6d1f5e5f8e7212ab48289191ae87c39e2a
| Timestamp: 1780776666 | Timestamp [UTC]: 2026-06-06 20:11:06 | Age [y:d:h:m:s]: 00:002:05:24:51 |
| Block: 6726 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1160 | RingCT/type: yes/0 |
| Extra: 016c021c5dfbf2ff45c550572c21ea9a6d1f5e5f8e7212ab48289191ae87c39e2a020900000001e49593ff00 | ||
1 output(s) for total of 34.735946657629 HMNY
| stealth address | amount | amount idx | tag |
| 00: 160375c4f7dc6e21b670e7c53dc86ced81fa7c3538d7c8ae89c7b907b9cf3d86 | 34.735946657629 | 8298 of 0 | <da> |
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": 6786,
"vin": [ {
"gen": {
"height": 6726
}
}
],
"vout": [ {
"amount": 34735946657629,
"target": {
"tagged_key": {
"key": "160375c4f7dc6e21b670e7c53dc86ced81fa7c3538d7c8ae89c7b907b9cf3d86",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 108, 2, 28, 93, 251, 242, 255, 69, 197, 80, 87, 44, 33, 234, 154, 109, 31, 94, 95, 142, 114, 18, 171, 72, 40, 145, 145, 174, 135, 195, 158, 42, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}