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: 094e6a0537df67eecf2387cb58cdce9341f89e50fae972ee584087a5b395265d
Tx prefix hash: 3a8f82eb8ace2b1d2691a71e8d7f44633a61fbd15c473b9e638116975ac4349b
Tx public key: b601631ccd2c2f3e0d56b877ba773e44f02d7d31c3f50db7ae5e5248f4efeef8
| Timestamp: 1780690205 | Timestamp [UTC]: 2026-06-05 20:10:05 | Age [y:d:h:m:s]: 00:003:20:58:58 |
| Block: 5645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3089 | RingCT/type: yes/0 |
| Extra: 01b601631ccd2c2f3e0d56b877ba773e44f02d7d31c3f50db7ae5e5248f4efeef8020900000001e49593ff00 | ||
1 output(s) for total of 34.807640710331 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8219f92f3cf672bd5e3e7c54f0dc20808df5a0150d8f06894f981cf2a2f7f7a | 34.807640710331 | 7094 of 0 | <3b> |
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": 5705,
"vin": [ {
"gen": {
"height": 5645
}
}
],
"vout": [ {
"amount": 34807640710331,
"target": {
"tagged_key": {
"key": "d8219f92f3cf672bd5e3e7c54f0dc20808df5a0150d8f06894f981cf2a2f7f7a",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 182, 1, 99, 28, 205, 44, 47, 62, 13, 86, 184, 119, 186, 119, 62, 68, 240, 45, 125, 49, 195, 245, 13, 183, 174, 94, 82, 72, 244, 239, 238, 248, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}