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: 512e469fdbd766e4157307c772a91c41c363ba889efd5916450e6cbdb6540392
Tx prefix hash: 32de685ffbbc3ea55608ef131e2c8b6a33df7658ffd901ce2ac3af8c21bc5dbb
Tx public key: 97a7b37423c28e434dd5caea9ca6da839c92e769373b7d36f135f8a2216a3d3c
| Timestamp: 1780738648 | Timestamp [UTC]: 2026-06-06 09:37:28 | Age [y:d:h:m:s]: 00:002:15:58:29 |
| Block: 6392 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1494 | RingCT/type: yes/0 |
| Extra: 0197a7b37423c28e434dd5caea9ca6da839c92e769373b7d36f135f8a2216a3d3c020900000001e49593ff00 | ||
1 output(s) for total of 34.758082417996 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b77655be8316f9d72f166881d0796ce0ad324f09b3e4878810ad673223d46ec | 34.758082417996 | 7881 of 0 | <a1> |
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": 6452,
"vin": [ {
"gen": {
"height": 6392
}
}
],
"vout": [ {
"amount": 34758082417996,
"target": {
"tagged_key": {
"key": "3b77655be8316f9d72f166881d0796ce0ad324f09b3e4878810ad673223d46ec",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 151, 167, 179, 116, 35, 194, 142, 67, 77, 213, 202, 234, 156, 166, 218, 131, 156, 146, 231, 105, 55, 59, 125, 54, 241, 53, 248, 162, 33, 106, 61, 60, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}