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: a9ed959ac2666044ca4aeeacad3f1f211c452496327c5b62a97a768e0352465f
Tx prefix hash: ea55d2fea86750741075bee34f780a78fb739a366f89560f789ab7ffa7d70f3f
Tx public key: fd1b9eba11bb4d3995ec15e34e1aded37e84c26360e4a07c7a547245c4a6a09f
| Timestamp: 1780704312 | Timestamp [UTC]: 2026-06-06 00:05:12 | Age [y:d:h:m:s]: 00:003:00:41:35 |
| Block: 6091 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1795 | RingCT/type: yes/0 |
| Extra: 01fd1b9eba11bb4d3995ec15e34e1aded37e84c26360e4a07c7a547245c4a6a09f020900000003e49593ff00 | ||
1 output(s) for total of 34.778043196419 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6b74d608eb9a5bf070a3a982baae86aa896ed4a6c34eee41f0f056c244f42f98 | 34.778043196419 | 7562 of 0 | <2e> |
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": 6151,
"vin": [ {
"gen": {
"height": 6091
}
}
],
"vout": [ {
"amount": 34778043196419,
"target": {
"tagged_key": {
"key": "6b74d608eb9a5bf070a3a982baae86aa896ed4a6c34eee41f0f056c244f42f98",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 253, 27, 158, 186, 17, 187, 77, 57, 149, 236, 21, 227, 78, 26, 222, 211, 126, 132, 194, 99, 96, 228, 160, 124, 122, 84, 114, 69, 196, 166, 160, 159, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}