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: 30a73ffdec259e19850414c9ea9ee1bd34a905a0943a889da55fc7cc795503a4
Tx prefix hash: c4fbd998f907bf144d2d73e0dfd09be3641dc787af8e55603c6650fa8440b1fb
Tx public key: 5e74e92ca152c82bdd58a19f5c60a00ca1a119d483a33ef056e9bdb0d1be41fa
| Timestamp: 1780037609 | Timestamp [UTC]: 2026-05-29 06:53:29 | Age [y:d:h:m:s]: 00:010:17:53:18 |
| Block: 4253 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3633 | RingCT/type: yes/0 |
| Extra: 015e74e92ca152c82bdd58a19f5c60a00ca1a119d483a33ef056e9bdb0d1be41fa02090000000126697be300 | ||
1 output(s) for total of 34.900178895861 HMNY
| stealth address | amount | amount idx | tag |
| 00: bcffbbdbf5da63dc9b7062366a7ce49e0272d95610ed05a43df7b95118892b3f | 34.900178895861 | 5310 of 0 | <25> |
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": 4313,
"vin": [ {
"gen": {
"height": 4253
}
}
],
"vout": [ {
"amount": 34900178895861,
"target": {
"tagged_key": {
"key": "bcffbbdbf5da63dc9b7062366a7ce49e0272d95610ed05a43df7b95118892b3f",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 94, 116, 233, 44, 161, 82, 200, 43, 221, 88, 161, 159, 92, 96, 160, 12, 161, 161, 25, 212, 131, 163, 62, 240, 86, 233, 189, 176, 209, 190, 65, 250, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}