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: f59927286312ca2ac77adb663e18b282130d00d2311c90f58d389fb85a778f5f
Tx prefix hash: 0d4e05117fc8acb1a53e91b421c8d99f637807c520df1e21987392973dd2a781
Tx public key: 0084201c475ed821ebf613d12f948705c834c77878a82dea54d498480bb02eb4
| Timestamp: 1780685007 | Timestamp [UTC]: 2026-06-05 18:43:27 | Age [y:d:h:m:s]: 00:003:06:03:20 |
| Block: 5369 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2517 | RingCT/type: yes/0 |
| Extra: 010084201c475ed821ebf613d12f948705c834c77878a82dea54d498480bb02eb4020900000002e49593ff00 | ||
1 output(s) for total of 34.825969276159 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ec8101e62b2e7289a64aaa4d3c10d79750be8a460d5cf4c212d3fdfd69febbf | 34.825969276159 | 6804 of 0 | <a2> |
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": 5429,
"vin": [ {
"gen": {
"height": 5369
}
}
],
"vout": [ {
"amount": 34825969276159,
"target": {
"tagged_key": {
"key": "3ec8101e62b2e7289a64aaa4d3c10d79750be8a460d5cf4c212d3fdfd69febbf",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 0, 132, 32, 28, 71, 94, 216, 33, 235, 246, 19, 209, 47, 148, 135, 5, 200, 52, 199, 120, 120, 168, 45, 234, 84, 212, 152, 72, 11, 176, 46, 180, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}