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: 60d5286662c2e73896c3c9fa42a5125393ee5e05560306e5ee82417720082285
Tx prefix hash: f05946ef3b9a3c42ef16f7d52b95b4789323a3d27fcc1191d5802105ff8f2b10
Tx public key: 55e1ab0e286dfb28a15637e29b31f533bceb7bf640b43079d4410f981de8966a
| Timestamp: 1780771619 | Timestamp [UTC]: 2026-06-06 18:46:59 | Age [y:d:h:m:s]: 00:002:06:48:58 |
| Block: 6671 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1215 | RingCT/type: yes/0 |
| Extra: 0155e1ab0e286dfb28a15637e29b31f533bceb7bf640b43079d4410f981de8966a020900000001e49593ff00 | ||
1 output(s) for total of 34.739590798064 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8213f116d6ca3efcf32d543790c6ba0527a52d58e8dd8a55c07adb3e0b91cc2a | 34.739590798064 | 8227 of 0 | <7c> |
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": 6731,
"vin": [ {
"gen": {
"height": 6671
}
}
],
"vout": [ {
"amount": 34739590798064,
"target": {
"tagged_key": {
"key": "8213f116d6ca3efcf32d543790c6ba0527a52d58e8dd8a55c07adb3e0b91cc2a",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 85, 225, 171, 14, 40, 109, 251, 40, 161, 86, 55, 226, 155, 49, 245, 51, 188, 235, 123, 246, 64, 180, 48, 121, 212, 65, 15, 152, 29, 232, 150, 106, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}