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: 66fe8892da3a261a44b1bc319888976e0fa3008c73cd7669346caca1619e3d2a
Tx prefix hash: 2ba964aeddf31a6f2f8c7368a27bad11a2ad755a18875f782d0a9f98c84c09c6
Tx public key: 8a40dfc69c478696bf107fba4dba9c72f6acdd08fb8daa0e0dd258bea28e9fe6
| Timestamp: 1780686000 | Timestamp [UTC]: 2026-06-05 19:00:00 | Age [y:d:h:m:s]: 00:003:06:35:57 |
| Block: 5408 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2478 | RingCT/type: yes/0 |
| Extra: 018a40dfc69c478696bf107fba4dba9c72f6acdd08fb8daa0e0dd258bea28e9fe6020900000001e49593ff00 | ||
1 output(s) for total of 34.823378784708 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f075457ee01e18816ee1dd6193ff78f97196824a34dcaa77c02f928e4ebc414 | 34.823378784708 | 6845 of 0 | <eb> |
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": 5468,
"vin": [ {
"gen": {
"height": 5408
}
}
],
"vout": [ {
"amount": 34823378784708,
"target": {
"tagged_key": {
"key": "2f075457ee01e18816ee1dd6193ff78f97196824a34dcaa77c02f928e4ebc414",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 138, 64, 223, 198, 156, 71, 134, 150, 191, 16, 127, 186, 77, 186, 156, 114, 246, 172, 221, 8, 251, 141, 170, 14, 13, 210, 88, 190, 162, 142, 159, 230, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}