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: 03798086b75bd3b15fbb38e5bb0a4968b56153e6b2bf3243953723c35fd7b3a6
Tx prefix hash: 5fd0e6ef68541d688d3028c990bbc6ef7bf9e984c344f9cc62dcdcdd1eb8a40d
Tx public key: 9e7340d8a87625f1c190d7fbcdef5082f4ed6f1199742f0fb6ea806bb5e4968b
| Timestamp: 1780695005 | Timestamp [UTC]: 2026-06-05 21:30:05 | Age [y:d:h:m:s]: 00:003:03:16:42 |
| Block: 5969 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1917 | RingCT/type: yes/0 |
| Extra: 019e7340d8a87625f1c190d7fbcdef5082f4ed6f1199742f0fb6ea806bb5e4968b020900000001e49593ff00 | ||
1 output(s) for total of 34.815994075870 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7c72770d77b8ce2664e1bc170ce01bdbcb9b42d01ace385ef224865cd3b5906 | 34.815994075870 | 7432 of 0 | <52> |
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": 6029,
"vin": [ {
"gen": {
"height": 5969
}
}
],
"vout": [ {
"amount": 34815994075870,
"target": {
"tagged_key": {
"key": "b7c72770d77b8ce2664e1bc170ce01bdbcb9b42d01ace385ef224865cd3b5906",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 158, 115, 64, 216, 168, 118, 37, 241, 193, 144, 215, 251, 205, 239, 80, 130, 244, 237, 111, 17, 153, 116, 47, 15, 182, 234, 128, 107, 181, 228, 150, 139, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}