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: d1df73b3bc19e9be31bbb8a4d46b8d8ba225caf1483473246d1917f2e623c06f
Tx prefix hash: ab65ae0ec4fb506e2a43bb4c4c6483b229f72c5b499ac02dc0cd48189f61dd37
Tx public key: 454d86a00cf68ad05f4cac3373a73e8b47e9c2dee82d038540a136ce1f016401
| Timestamp: 1779961572 | Timestamp [UTC]: 2026-05-28 09:46:12 | Age [y:d:h:m:s]: 00:016:01:34:53 |
| Block: 3764 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4981 | RingCT/type: yes/0 |
| Extra: 01454d86a00cf68ad05f4cac3373a73e8b47e9c2dee82d038540a136ce1f01640102090000000226697be300 | ||
1 output(s) for total of 34.932745281143 HMNY
| stealth address | amount | amount idx | tag |
| 00: f21ff3eafcb8e94e9a985b671af7e1d895c0529c09ef7e2c40e1da7ce074c47a | 34.932745281143 | 4565 of 0 | <d7> |
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": 3824,
"vin": [ {
"gen": {
"height": 3764
}
}
],
"vout": [ {
"amount": 34932745281143,
"target": {
"tagged_key": {
"key": "f21ff3eafcb8e94e9a985b671af7e1d895c0529c09ef7e2c40e1da7ce074c47a",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 69, 77, 134, 160, 12, 246, 138, 208, 95, 76, 172, 51, 115, 167, 62, 139, 71, 233, 194, 222, 232, 45, 3, 133, 64, 161, 54, 206, 31, 1, 100, 1, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}