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: c47b77a5de7d71fd674fca0e18556eae7c233c482bbecfb0cd3ef52405f9e803
Tx prefix hash: 1f98b498eb6c761c07764cd25a97f525acec3386bde14a14edb7928328ad4045
Tx public key: 18d718a600677f89f3097e86f2f3713c1f95c28d9ab5cafbf0dca485282d1b9a
| Timestamp: 1780756475 | Timestamp [UTC]: 2026-06-06 14:34:35 | Age [y:d:h:m:s]: 00:002:13:04:15 |
| Block: 6536 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1406 | RingCT/type: yes/0 |
| Extra: 0118d718a600677f89f3097e86f2f3713c1f95c28d9ab5cafbf0dca485282d1b9a020900000001e49593ff00 | ||
1 output(s) for total of 34.748537127338 HMNY
| stealth address | amount | amount idx | tag |
| 00: a04d853f5819c6a675bdd68d1ab328f1b2a98369dbbdc6444a41e2a3a88b9af2 | 34.748537127338 | 8042 of 0 | <76> |
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": 6596,
"vin": [ {
"gen": {
"height": 6536
}
}
],
"vout": [ {
"amount": 34748537127338,
"target": {
"tagged_key": {
"key": "a04d853f5819c6a675bdd68d1ab328f1b2a98369dbbdc6444a41e2a3a88b9af2",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 24, 215, 24, 166, 0, 103, 127, 137, 243, 9, 126, 134, 242, 243, 113, 60, 31, 149, 194, 141, 154, 181, 202, 251, 240, 220, 164, 133, 40, 45, 27, 154, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}