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: e033fbf7930ea743ce8567f747fd308c4b673cef49779db88aabb8a496ffe19e
Tx prefix hash: 8f883cf08bca95856bf8d51682d37f002257d3ee133519fed0e8c6eab3b51789
Tx public key: a66f67a33149c79fb6ffda9823db750f86fdbccb367ab424394b9dc32a91c3a7
| Timestamp: 1780694777 | Timestamp [UTC]: 2026-06-05 21:26:17 | Age [y:d:h:m:s]: 00:011:10:35:28 |
| Block: 5960 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2785 | RingCT/type: yes/0 |
| Extra: 01a66f67a33149c79fb6ffda9823db750f86fdbccb367ab424394b9dc32a91c3a7020900000001e49593ff00 | ||
1 output(s) for total of 34.786734025180 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4b9ed13d37784bc4ad3acb8fc6a4fec60a90c84eced8ce3f72824f0056d0b974 | 34.786734025180 | 7423 of 0 | <fb> |
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": 6020,
"vin": [ {
"gen": {
"height": 5960
}
}
],
"vout": [ {
"amount": 34786734025180,
"target": {
"tagged_key": {
"key": "4b9ed13d37784bc4ad3acb8fc6a4fec60a90c84eced8ce3f72824f0056d0b974",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 166, 111, 103, 163, 49, 73, 199, 159, 182, 255, 218, 152, 35, 219, 117, 15, 134, 253, 188, 203, 54, 122, 180, 36, 57, 75, 157, 195, 42, 145, 195, 167, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}