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: d307491a99f4f9e4f719bf18f8349518cf3ed17f4c4cba25c004902bd84f13db
Tx prefix hash: a5628c7514f45bb01ff266e14bddc01a43dabfff676369f9d256cc60725ce05f
Tx public key: 6c6a9082ae3cf700fa387f7a704f68b1394670609d0e8e764004147c1f78ecf2
| Timestamp: 1780863706 | Timestamp [UTC]: 2026-06-07 20:21:46 | Age [y:d:h:m:s]: 00:001:06:18:50 |
| Block: 7642 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 255 | RingCT/type: yes/0 |
| Extra: 016c6a9082ae3cf700fa387f7a704f68b1394670609d0e8e764004147c1f78ecf2020900000005e49593ff00 | ||
1 output(s) for total of 34.675311322878 HMNY
| stealth address | amount | amount idx | tag |
| 00: f2ae9cf50477203a990c8b6eec523457a7a1a58d1c346e9530c23c0c7fee363d | 34.675311322878 | 9448 of 0 | <05> |
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": 7702,
"vin": [ {
"gen": {
"height": 7642
}
}
],
"vout": [ {
"amount": 34675311322878,
"target": {
"tagged_key": {
"key": "f2ae9cf50477203a990c8b6eec523457a7a1a58d1c346e9530c23c0c7fee363d",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 108, 106, 144, 130, 174, 60, 247, 0, 250, 56, 127, 122, 112, 79, 104, 177, 57, 70, 112, 96, 157, 14, 142, 118, 64, 4, 20, 124, 31, 120, 236, 242, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}