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: 5ef619603fd2a0906981ef5c22d2856f0d8073e5c15c3257f6efc2441c2f8143
Tx prefix hash: f176ca743c3cf40e65aaa434c3b4d1d448c87b55c548f98d17bad831919ab313
Tx public key: de6318043c05acb3a6f2e0b6fd974ddaa2ea7a480d6b30313e66db38c4e4507d
| Timestamp: 1779637777 | Timestamp [UTC]: 2026-05-24 15:49:37 | Age [y:d:h:m:s]: 00:015:09:46:20 |
| Block: 1170 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6716 | RingCT/type: yes/0 |
| Extra: 01de6318043c05acb3a6f2e0b6fd974ddaa2ea7a480d6b30313e66db38c4e4507d020900000001ba6d17be00 | ||
1 output(s) for total of 35.106009147217 HMNY
| stealth address | amount | amount idx | tag |
| 00: 945b68c2ec97f94d0ebeb6bd70ba85030170fc230ceb77d4f074f40aff6db741 | 35.106009147217 | 1314 of 0 | <11> |
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": 1230,
"vin": [ {
"gen": {
"height": 1170
}
}
],
"vout": [ {
"amount": 35106009147217,
"target": {
"tagged_key": {
"key": "945b68c2ec97f94d0ebeb6bd70ba85030170fc230ceb77d4f074f40aff6db741",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 222, 99, 24, 4, 60, 5, 172, 179, 166, 242, 224, 182, 253, 151, 77, 218, 162, 234, 122, 72, 13, 107, 48, 49, 62, 102, 219, 56, 196, 228, 80, 125, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}