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: 46e3d44b62158bbfc4f0c713466adc5fb1e2599fdb0f0f29885f4f1cbe0c572e
Tx prefix hash: 90bcd824c80b40409ccc5e8ffb29a995bcc5e8abb6c18e01bbfebaed8425da5b
Tx public key: 4e0ea4a8308d37e950c232f73cb8494e801e32ff787c5abeefc3831c1c53dea1
| Timestamp: 1780689432 | Timestamp [UTC]: 2026-06-05 19:57:12 | Age [y:d:h:m:s]: 00:003:05:38:45 |
| Block: 5594 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2292 | RingCT/type: yes/0 |
| Extra: 014e0ea4a8308d37e950c232f73cb8494e801e32ff787c5abeefc3831c1c53dea1020900000001e49593ff00 | ||
1 output(s) for total of 34.811026783850 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd9082991511a7ca598a273d7026a3f09d946dba322d85675d933cd1d5f8ce63 | 34.811026783850 | 7039 of 0 | <a9> |
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": 5654,
"vin": [ {
"gen": {
"height": 5594
}
}
],
"vout": [ {
"amount": 34811026783850,
"target": {
"tagged_key": {
"key": "dd9082991511a7ca598a273d7026a3f09d946dba322d85675d933cd1d5f8ce63",
"view_tag": "a9"
}
}
}
],
"extra": [ 1, 78, 14, 164, 168, 48, 141, 55, 233, 80, 194, 50, 247, 60, 184, 73, 78, 128, 30, 50, 255, 120, 124, 90, 190, 239, 195, 131, 28, 28, 83, 222, 161, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}