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: 0cc67bf7798728d3bfe3039a2a5f7bc61b64bb037b95912794f8058d7f313d48
Tx prefix hash: 96ceeba8e2de204beb958e1ba3524d46c99097749452a65b60a3eecd3ee0698d
Tx public key: f3afbd467383403f3d904394105f1f2cf82060c0571f0a4ff5799871aa8828d8
| Timestamp: 1780775225 | Timestamp [UTC]: 2026-06-06 19:47:05 | Age [y:d:h:m:s]: 00:002:09:51:34 |
| Block: 6714 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1419 | RingCT/type: yes/0 |
| Extra: 01f3afbd467383403f3d904394105f1f2cf82060c0571f0a4ff5799871aa8828d8020900000003e49593ff00 | ||
1 output(s) for total of 34.736741710210 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4c047da71d43c70184d2348f1ceb9168feaef45bb1a784660482b4628c2a8e67 | 34.736741710210 | 8280 of 0 | <8e> |
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": 6774,
"vin": [ {
"gen": {
"height": 6714
}
}
],
"vout": [ {
"amount": 34736741710210,
"target": {
"tagged_key": {
"key": "4c047da71d43c70184d2348f1ceb9168feaef45bb1a784660482b4628c2a8e67",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 243, 175, 189, 70, 115, 131, 64, 63, 61, 144, 67, 148, 16, 95, 31, 44, 248, 32, 96, 192, 87, 31, 10, 79, 245, 121, 152, 113, 170, 136, 40, 216, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}