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: 6f871ac87de159455ababfc1d8a1724ef1c7e60f0cae93d03b7845cf5311e23c
Tx prefix hash: f0ba16caa7a1ff2abce4b92a69ccc5b37b55b286d796f8d9d69db1c0d0ca297c
Tx public key: 2fab9946657d406182f07d0e74404d2a03ac9692c6b8ded52b7a6e8e49b9c900
| Timestamp: 1779714237 | Timestamp [UTC]: 2026-05-25 13:03:57 | Age [y:d:h:m:s]: 00:014:10:14:56 |
| Block: 1613 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6273 | RingCT/type: yes/0 |
| Extra: 012fab9946657d406182f07d0e74404d2a03ac9692c6b8ded52b7a6e8e49b9c900020900000002ba6d17be00 | ||
1 output(s) for total of 35.076358633828 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5564ce1a43a07e145ca452c6ea9225a50964778a062a4ff52411f8f3f2863f4 | 35.076358633828 | 1771 of 0 | <5a> |
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": 1673,
"vin": [ {
"gen": {
"height": 1613
}
}
],
"vout": [ {
"amount": 35076358633828,
"target": {
"tagged_key": {
"key": "c5564ce1a43a07e145ca452c6ea9225a50964778a062a4ff52411f8f3f2863f4",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 47, 171, 153, 70, 101, 125, 64, 97, 130, 240, 125, 14, 116, 64, 77, 42, 3, 172, 150, 146, 198, 184, 222, 213, 43, 122, 110, 142, 73, 185, 201, 0, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}