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: f66b2c01f33153dfaba6d509cd8358a7679afbd42c58ca1142d255893b91e520
Tx prefix hash: d076893fed8d811388f981e4738ef5b10786be7005d4e376bf601bc175dfbaf1
Tx public key: c6d9429469083eae4187a39bb0f576fcd1129ecb680c3dd2904ca741947a1f7e
| Timestamp: 1780760899 | Timestamp [UTC]: 2026-06-06 15:48:19 | Age [y:d:h:m:s]: 00:002:08:58:28 |
| Block: 6566 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1320 | RingCT/type: yes/0 |
| Extra: 01c6d9429469083eae4187a39bb0f576fcd1129ecb680c3dd2904ca741947a1f7e020900000004e49593ff00 | ||
1 output(s) for total of 34.746548855084 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6fdb428c73d8fafad57e55f4e84751aa07e7d5089fa9bb2a5e1008948af08619 | 34.746548855084 | 8086 of 0 | <e6> |
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": 6626,
"vin": [ {
"gen": {
"height": 6566
}
}
],
"vout": [ {
"amount": 34746548855084,
"target": {
"tagged_key": {
"key": "6fdb428c73d8fafad57e55f4e84751aa07e7d5089fa9bb2a5e1008948af08619",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 198, 217, 66, 148, 105, 8, 62, 174, 65, 135, 163, 155, 176, 245, 118, 252, 209, 18, 158, 203, 104, 12, 61, 210, 144, 76, 167, 65, 148, 122, 31, 126, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}