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: 9a34e30cf38b4c169b6d2c4d3912fa7e9ff525c9a9cd65f31f46464b4ee21543
Tx prefix hash: 8e7f9e6e5f2ccafd59f69bd531d913ac814fec0585406e88aa8f15883ca1ddfe
Tx public key: 2d6cb5f87ffb4fab635d891c2bfd190acc454f40f034dfe1b0c3af8fbb3c3c77
| Timestamp: 1780894159 | Timestamp [UTC]: 2026-06-08 04:49:19 | Age [y:d:h:m:s]: 00:000:20:46:38 |
| Block: 7753 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 133 | RingCT/type: yes/0 |
| Extra: 012d6cb5f87ffb4fab635d891c2bfd190acc454f40f034dfe1b0c3af8fbb3c3c770209000000014a728a4c00 | ||
1 output(s) for total of 34.667970785210 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5214bcb1b95c0a7f998fc32b5e0fc5fcfd45cc49270bde092570326b18e956b9 | 34.667970785210 | 9599 of 0 | <d3> |
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": 7813,
"vin": [ {
"gen": {
"height": 7753
}
}
],
"vout": [ {
"amount": 34667970785210,
"target": {
"tagged_key": {
"key": "5214bcb1b95c0a7f998fc32b5e0fc5fcfd45cc49270bde092570326b18e956b9",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 45, 108, 181, 248, 127, 251, 79, 171, 99, 93, 137, 28, 43, 253, 25, 10, 204, 69, 79, 64, 240, 52, 223, 225, 176, 195, 175, 143, 187, 60, 60, 119, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}