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: 79578baa9876089e39d787d30ed92b883449a3e9c4652bf8abe5391e82f0f99d
Tx prefix hash: 5532bf425cc1f052b23db37a38bd375391da067693648f65873502c491384c55
Tx public key: c27fe2d12d4488a5a1c8c65a2c864a1780d4ae73aa171ffb2a5dc5ec5593021b
| Timestamp: 1779716950 | Timestamp [UTC]: 2026-05-25 13:49:10 | Age [y:d:h:m:s]: 00:014:11:46:47 |
| Block: 1668 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6218 | RingCT/type: yes/0 |
| Extra: 01c27fe2d12d4488a5a1c8c65a2c864a1780d4ae73aa171ffb2a5dc5ec5593021b020900000001ba6d17be00 | ||
1 output(s) for total of 35.072679166860 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3200c849c6fdc677e89f4f7c53e6dee78b9a28cbbec77c55711f54a49c36e0dc | 35.072679166860 | 1832 of 0 | <94> |
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": 1728,
"vin": [ {
"gen": {
"height": 1668
}
}
],
"vout": [ {
"amount": 35072679166860,
"target": {
"tagged_key": {
"key": "3200c849c6fdc677e89f4f7c53e6dee78b9a28cbbec77c55711f54a49c36e0dc",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 194, 127, 226, 209, 45, 68, 136, 165, 161, 200, 198, 90, 44, 134, 74, 23, 128, 212, 174, 115, 170, 23, 31, 251, 42, 93, 197, 236, 85, 147, 2, 27, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}