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: b1d1a45663ecdc38c17f554e1c5b098c329fcaaac42a9e0310709632e974f715
Tx prefix hash: 2d4ab4b068c2b1f644e56f27e7d82226dead7a44f2fdd24cb050dad445b9d699
Tx public key: 1bf6128aba643203832d6b1e2cfd748a67e142f0ed767de837e370f33db27dfd
| Timestamp: 1780809442 | Timestamp [UTC]: 2026-06-07 05:17:22 | Age [y:d:h:m:s]: 00:001:19:29:25 |
| Block: 6999 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 887 | RingCT/type: yes/0 |
| Extra: 011bf6128aba643203832d6b1e2cfd748a67e142f0ed767de837e370f33db27dfd020900000002e49593ff00 | ||
1 output(s) for total of 34.717864126656 HMNY
| stealth address | amount | amount idx | tag |
| 00: 106ceffaa11a909343d18b7e7eaabefbbfcb07c789de7e670c999457fbb11bb2 | 34.717864126656 | 8631 of 0 | <b5> |
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": 7059,
"vin": [ {
"gen": {
"height": 6999
}
}
],
"vout": [ {
"amount": 34717864126656,
"target": {
"tagged_key": {
"key": "106ceffaa11a909343d18b7e7eaabefbbfcb07c789de7e670c999457fbb11bb2",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 27, 246, 18, 138, 186, 100, 50, 3, 131, 45, 107, 30, 44, 253, 116, 138, 103, 225, 66, 240, 237, 118, 125, 232, 55, 227, 112, 243, 61, 178, 125, 253, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}