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: 4bbc211e6f6de780c3d1a929913f8f75f9aab46ec3cfbcb4746e8de4563f3830
Tx prefix hash: 230e332562c45e7072d463d5bcaf4190b3eacf143c9da0b7ce2d603f22d2ee29
Tx public key: f69ebbeb6972096c52502443750e2c1e6ec65b4fc85e02084550f31f0061e90c
| Timestamp: 1780826387 | Timestamp [UTC]: 2026-06-07 09:59:47 | Age [y:d:h:m:s]: 00:001:15:36:10 |
| Block: 7274 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 612 | RingCT/type: yes/0 |
| Extra: 01f69ebbeb6972096c52502443750e2c1e6ec65b4fc85e02084550f31f0061e90c020900000002e49593ff00 | ||
1 output(s) for total of 34.699658639854 HMNY
| stealth address | amount | amount idx | tag |
| 00: de74f107e3124ec9a5aa4b499b5dc162b353e6aa408b9f5bfc54928f0a594b62 | 34.699658639854 | 8956 of 0 | <af> |
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": 7334,
"vin": [ {
"gen": {
"height": 7274
}
}
],
"vout": [ {
"amount": 34699658639854,
"target": {
"tagged_key": {
"key": "de74f107e3124ec9a5aa4b499b5dc162b353e6aa408b9f5bfc54928f0a594b62",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 246, 158, 187, 235, 105, 114, 9, 108, 82, 80, 36, 67, 117, 14, 44, 30, 110, 198, 91, 79, 200, 94, 2, 8, 69, 80, 243, 31, 0, 97, 233, 12, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}