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: 2c990ec3e60f0df3467e19eaafb8589641473b4caad2802419774b3468a4ec16
Tx prefix hash: a43bf0096d5a2f71ccbe5514a6d0a894f0dcb8dc379efc908f090649ab9c1c8b
Tx public key: bd93fb5c4fc8bd21c21cfdefa108c1d6dac69e4568b9e9a0837e19d0d4456cbb
| Timestamp: 1780729625 | Timestamp [UTC]: 2026-06-06 07:07:05 | Age [y:d:h:m:s]: 00:002:18:28:52 |
| Block: 6303 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1583 | RingCT/type: yes/0 |
| Extra: 01bd93fb5c4fc8bd21c21cfdefa108c1d6dac69e4568b9e9a0837e19d0d4456cbb020900000004e49593ff00 | ||
1 output(s) for total of 34.763983248961 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1fdc6f14d0380252364db1a319dad2cf1487eb1666e18170c13752cbdfb6757 | 34.763983248961 | 7788 of 0 | <c0> |
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": 6363,
"vin": [ {
"gen": {
"height": 6303
}
}
],
"vout": [ {
"amount": 34763983248961,
"target": {
"tagged_key": {
"key": "a1fdc6f14d0380252364db1a319dad2cf1487eb1666e18170c13752cbdfb6757",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 189, 147, 251, 92, 79, 200, 189, 33, 194, 28, 253, 239, 161, 8, 193, 214, 218, 198, 158, 69, 104, 185, 233, 160, 131, 126, 25, 208, 212, 69, 108, 187, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}