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: d2bde86b28a044362224243e90a0f93419fe9a772832b6b1efc62fcf1742d20f
Tx prefix hash: c3ab4851a60ed273c3f5eab7888b1b1dbacbe98601ac6385c15d6882b7ac0e72
Tx public key: 929a7ac124ecd0fd8dbf34f8e9e2621662e0eaa555dd3ec7ae0c9ae35f101530
| Timestamp: 1781008677 | Timestamp [UTC]: 2026-06-09 12:37:57 | Age [y:d:h:m:s]: 00:006:00:02:12 |
| Block: 8572 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 173 | RingCT/type: yes/0 |
| Extra: 01929a7ac124ecd0fd8dbf34f8e9e2621662e0eaa555dd3ec7ae0c9ae35f101530020900000001e49593ff00 | ||
1 output(s) for total of 34.613857530696 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1e105f9a8522b821e5d247e228e8a59d643b37db86e5720e9a397fbe9952a05 | 34.613857530696 | 10588 of 0 | <89> |
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": 8632,
"vin": [ {
"gen": {
"height": 8572
}
}
],
"vout": [ {
"amount": 34613857530696,
"target": {
"tagged_key": {
"key": "d1e105f9a8522b821e5d247e228e8a59d643b37db86e5720e9a397fbe9952a05",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 146, 154, 122, 193, 36, 236, 208, 253, 141, 191, 52, 248, 233, 226, 98, 22, 98, 224, 234, 165, 85, 221, 62, 199, 174, 12, 154, 227, 95, 16, 21, 48, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}