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: d3ff2f03bb210760d3c1c7cfbda4c24e5cbe93d305d64eecf7a5bff36f0141e5
Tx prefix hash: 091812c3fcc4a13b2c58daa60d8ce5c9c2ee6f127f5e19eeadc51917a708c7b7
Tx public key: cbb328dff6856422c00dc654a12de74be13911e4546b2b6e9be00573f19e4631
| Timestamp: 1780057556 | Timestamp [UTC]: 2026-05-29 12:25:56 | Age [y:d:h:m:s]: 00:011:04:43:07 |
| Block: 4471 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4263 | RingCT/type: yes/0 |
| Extra: 01cbb328dff6856422c00dc654a12de74be13911e4546b2b6e9be00573f19e463102090000000326697be300 | ||
1 output(s) for total of 34.885670334324 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf04b817a1033a0dd026f2cc328320e570eaed2fd36e8be97d6b22725ed5d95e | 34.885670334324 | 5601 of 0 | <9f> |
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": 4531,
"vin": [ {
"gen": {
"height": 4471
}
}
],
"vout": [ {
"amount": 34885670334324,
"target": {
"tagged_key": {
"key": "cf04b817a1033a0dd026f2cc328320e570eaed2fd36e8be97d6b22725ed5d95e",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 203, 179, 40, 223, 246, 133, 100, 34, 192, 13, 198, 84, 161, 45, 231, 75, 225, 57, 17, 228, 84, 107, 43, 110, 155, 224, 5, 115, 241, 158, 70, 49, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}