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: b32caca7d4bce909fa7696a65f407a77896d8274ebe9298b8b0e5c6e7dfe2274
Tx prefix hash: d467dbe9d0d2a84ea0c2a9d91d6e457203c9008db732d604f27214e1b04cc1f3
Tx public key: 6bb88b094db4dc2858b711e8730e5527dc219b4f0f63c5bd8df6dddbeb547e45
| Timestamp: 1780733973 | Timestamp [UTC]: 2026-06-06 08:19:33 | Age [y:d:h:m:s]: 00:002:16:27:14 |
| Block: 6344 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1542 | RingCT/type: yes/0 |
| Extra: 016bb88b094db4dc2858b711e8730e5527dc219b4f0f63c5bd8df6dddbeb547e45020900000001e49593ff00 | ||
1 output(s) for total of 34.761264764192 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5414cfcbaab1a593bc61ac49d93306e4efa55b90c448a10dfe0cdd3e89007945 | 34.761264764192 | 7831 of 0 | <ea> |
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": 6404,
"vin": [ {
"gen": {
"height": 6344
}
}
],
"vout": [ {
"amount": 34761264764192,
"target": {
"tagged_key": {
"key": "5414cfcbaab1a593bc61ac49d93306e4efa55b90c448a10dfe0cdd3e89007945",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 107, 184, 139, 9, 77, 180, 220, 40, 88, 183, 17, 232, 115, 14, 85, 39, 220, 33, 155, 79, 15, 99, 197, 189, 141, 246, 221, 219, 235, 84, 126, 69, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}