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: 3a237d8880892b044da486e31ce5cb531b79836f6efd8063b4675be1354e2b83
Tx prefix hash: 23e57f1f0efaa6ecb1ebd5dd580bdb39a47d2b78a7fd489945943afc3cbf512f
Tx public key: bd986795ba4e0fe5c5032423f99e1396efc8c5d7d0e04403b946d5c891c0fc50
| Timestamp: 1780323272 | Timestamp [UTC]: 2026-06-01 14:14:32 | Age [y:d:h:m:s]: 00:013:18:05:03 |
| Block: 5094 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3651 | RingCT/type: yes/0 |
| Extra: 01bd986795ba4e0fe5c5032423f99e1396efc8c5d7d0e04403b946d5c891c0fc5002090000001526697be300 | ||
1 output(s) for total of 34.844241032968 HMNY
| stealth address | amount | amount idx | tag |
| 00: c00c3c699bdeca5f1937db2e2e16816e274c6da2170bc167bca7617225daaf99 | 34.844241032968 | 6469 of 0 | <8f> |
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": 5154,
"vin": [ {
"gen": {
"height": 5094
}
}
],
"vout": [ {
"amount": 34844241032968,
"target": {
"tagged_key": {
"key": "c00c3c699bdeca5f1937db2e2e16816e274c6da2170bc167bca7617225daaf99",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 189, 152, 103, 149, 186, 78, 15, 229, 197, 3, 36, 35, 249, 158, 19, 150, 239, 200, 197, 215, 208, 224, 68, 3, 185, 70, 213, 200, 145, 192, 252, 80, 2, 9, 0, 0, 0, 21, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}