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: 5575cd074f424924361596f82767ae3904a1084d715229b37b2ba37f2d6cee65
Tx prefix hash: b1add645dccba4d0303cc1b3d68e2114d4b2a18dfd4d37fefba1b82b30b8fb36
Tx public key: d5907f9be69c7556bc1e35efe717c2d1ae0b13977b4534b1f001289519816587
| Timestamp: 1779469915 | Timestamp [UTC]: 2026-05-22 17:11:55 | Age [y:d:h:m:s]: 00:017:10:26:55 |
| Block: 551 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7391 | RingCT/type: yes/0 |
| Extra: 01d5907f9be69c7556bc1e35efe717c2d1ae0b13977b4534b1f00128951981658702090000000293369e7d00 | ||
1 output(s) for total of 35.147481531814 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d70336f1d29e986fcb1f65c0626ab50f98ef8a0f000bd270a5ca5c8c8bf42ec | 35.147481531814 | 557 of 0 | <db> |
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": 611,
"vin": [ {
"gen": {
"height": 551
}
}
],
"vout": [ {
"amount": 35147481531814,
"target": {
"tagged_key": {
"key": "2d70336f1d29e986fcb1f65c0626ab50f98ef8a0f000bd270a5ca5c8c8bf42ec",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 213, 144, 127, 155, 230, 156, 117, 86, 188, 30, 53, 239, 231, 23, 194, 209, 174, 11, 19, 151, 123, 69, 52, 177, 240, 1, 40, 149, 25, 129, 101, 135, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}