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: c4a83f9320b1947aadd18398aea4042e6a3d1b0f5026a2397f9e262f9c01eedf
Tx prefix hash: 07a122b0128d4cc1ce5004f9966afdc957f844f521b5a4d6b42176a52d47dc69
Tx public key: 1db0f19ed2884ec0f87aeb0b4d2a689eedbe35353de71029f6e39134fc79d835
| Timestamp: 1780708211 | Timestamp [UTC]: 2026-06-06 01:10:11 | Age [y:d:h:m:s]: 00:002:22:08:42 |
| Block: 6137 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1749 | RingCT/type: yes/0 |
| Extra: 011db0f19ed2884ec0f87aeb0b4d2a689eedbe35353de71029f6e39134fc79d835020900000001e49593ff00 | ||
1 output(s) for total of 34.774991970121 HMNY
| stealth address | amount | amount idx | tag |
| 00: 45c5220ae1a962a8b865392bcf3ccedd56e02eb6f4a9fbb2c5067d17579817da | 34.774991970121 | 7612 of 0 | <0c> |
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": 6197,
"vin": [ {
"gen": {
"height": 6137
}
}
],
"vout": [ {
"amount": 34774991970121,
"target": {
"tagged_key": {
"key": "45c5220ae1a962a8b865392bcf3ccedd56e02eb6f4a9fbb2c5067d17579817da",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 29, 176, 241, 158, 210, 136, 78, 192, 248, 122, 235, 11, 77, 42, 104, 158, 237, 190, 53, 53, 61, 231, 16, 41, 246, 227, 145, 52, 252, 121, 216, 53, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}