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: 490c3d278e6d3d6ad8242db8769fa743c7ea2f58266664d65ee6a99ec2f376ea
Tx prefix hash: d324904a9d7f91bf91db903243dba7d8fc41e1ea1c3891b56dd52ebe382d696b
Tx public key: 5dabcc290258854d1b2d5d854111a8aa67b64eaf2f83e2ebd4e4973b748e919d
| Timestamp: 1779465558 | Timestamp [UTC]: 2026-05-22 15:59:18 | Age [y:d:h:m:s]: 00:017:10:41:18 |
| Block: 503 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7393 | RingCT/type: yes/0 |
| Extra: 015dabcc290258854d1b2d5d854111a8aa67b64eaf2f83e2ebd4e4973b748e919d02090000000393369e7d00 | ||
1 output(s) for total of 35.150699530230 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc0045040343072b84caa732858437760d76d7b184f564e48cc007a63aee913a | 35.150699530230 | 507 of 0 | <78> |
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": 563,
"vin": [ {
"gen": {
"height": 503
}
}
],
"vout": [ {
"amount": 35150699530230,
"target": {
"tagged_key": {
"key": "bc0045040343072b84caa732858437760d76d7b184f564e48cc007a63aee913a",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 93, 171, 204, 41, 2, 88, 133, 77, 27, 45, 93, 133, 65, 17, 168, 170, 103, 182, 78, 175, 47, 131, 226, 235, 212, 228, 151, 59, 116, 142, 145, 157, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}