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: bbab809830d022d07887e4a18ed068e61b7eb6d52488f6a7bc90825d6b1fb34d
Tx prefix hash: 5e71b347526a2109e90b8efd90b0cba475fdffd7c5cfb32c7d8fee1ca3d94e9b
Tx public key: cdb3a7c3ff3d19784e6cfb7fdaa5da47f5bf0d953831ab4aba58805beb047068
| Timestamp: 1780771307 | Timestamp [UTC]: 2026-06-06 18:41:47 | Age [y:d:h:m:s]: 00:002:06:54:10 |
| Block: 6667 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1219 | RingCT/type: yes/0 |
| Extra: 01cdb3a7c3ff3d19784e6cfb7fdaa5da47f5bf0d953831ab4aba58805beb047068020900000002e49593ff00 | ||
1 output(s) for total of 34.739855841372 HMNY
| stealth address | amount | amount idx | tag |
| 00: 598a710c6efab125bde53cde4be7d59867563148c19a40d2b30acf028ef9e21a | 34.739855841372 | 8223 of 0 | <71> |
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": 6727,
"vin": [ {
"gen": {
"height": 6667
}
}
],
"vout": [ {
"amount": 34739855841372,
"target": {
"tagged_key": {
"key": "598a710c6efab125bde53cde4be7d59867563148c19a40d2b30acf028ef9e21a",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 205, 179, 167, 195, 255, 61, 25, 120, 78, 108, 251, 127, 218, 165, 218, 71, 245, 191, 13, 149, 56, 49, 171, 74, 186, 88, 128, 91, 235, 4, 112, 104, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}