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: 1170a8fe539bfe66df6db384564e3e2566dd37cb2768ec1b8e14e5430c3dda47
Tx prefix hash: e8a42beff816bc57ffc2fa320525a2d5711125ae2e5787a761d91a66732c4950
Tx public key: 9e0d84882e9e172c0fae5e0f3b0e7057f0dfaabdfe213b98ac0f9c3eb2784e38
| Timestamp: 1780801860 | Timestamp [UTC]: 2026-06-07 03:11:00 | Age [y:d:h:m:s]: 00:001:22:24:57 |
| Block: 6853 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1033 | RingCT/type: yes/0 |
| Extra: 019e0d84882e9e172c0fae5e0f3b0e7057f0dfaabdfe213b98ac0f9c3eb2784e38020900000003e49593ff00 | ||
1 output(s) for total of 34.727533466458 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9ae2b451821a727bd69cf77ab3e6159fae1e32dc62db164a0d97ed15b296aef1 | 34.727533466458 | 8461 of 0 | <60> |
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": 6913,
"vin": [ {
"gen": {
"height": 6853
}
}
],
"vout": [ {
"amount": 34727533466458,
"target": {
"tagged_key": {
"key": "9ae2b451821a727bd69cf77ab3e6159fae1e32dc62db164a0d97ed15b296aef1",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 158, 13, 132, 136, 46, 158, 23, 44, 15, 174, 94, 15, 59, 14, 112, 87, 240, 223, 170, 189, 254, 33, 59, 152, 172, 15, 156, 62, 178, 120, 78, 56, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}