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: 545a493325bb91a3ac55f3c56d42aea72524e0f06eab8824c7337b93b88b0ffe
Tx prefix hash: 36796ea149226749563659a7d267d4a01f5e8b01125efe77f5f4cff2aae8fe31
Tx public key: 8ad9f54d5d814f8dd632b622c5a241790131afbad7f94d9ad3f6e0152e1cb0b7
| Timestamp: 1780836495 | Timestamp [UTC]: 2026-06-07 12:48:15 | Age [y:d:h:m:s]: 00:001:12:47:42 |
| Block: 7415 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 471 | RingCT/type: yes/0 |
| Extra: 018ad9f54d5d814f8dd632b622c5a241790131afbad7f94d9ad3f6e0152e1cb0b7020900000001e49593ff00 | ||
1 output(s) for total of 34.690327892848 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0981f428a1d1e95189abeb40a341e7f8b10215610992a5ff4fe80f2dd71dedf3 | 34.690327892848 | 9129 of 0 | <b8> |
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": 7475,
"vin": [ {
"gen": {
"height": 7415
}
}
],
"vout": [ {
"amount": 34690327892848,
"target": {
"tagged_key": {
"key": "0981f428a1d1e95189abeb40a341e7f8b10215610992a5ff4fe80f2dd71dedf3",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 138, 217, 245, 77, 93, 129, 79, 141, 214, 50, 182, 34, 197, 162, 65, 121, 1, 49, 175, 186, 215, 249, 77, 154, 211, 246, 224, 21, 46, 28, 176, 183, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}