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: e5c4c2b250567b6d6c08d1f767591376ea90484e92c1137d8757665b540f2f1d
Tx prefix hash: 7af80e14695c6f451dc97387673ce67bec1ef465b48d4babb9ad3494625157c1
Tx public key: 16a9b3d1f2b8d06a0cc06a8a0d891bd6f3f9458edef08e19742de64156318a92
| Timestamp: 1780761823 | Timestamp [UTC]: 2026-06-06 16:03:43 | Age [y:d:h:m:s]: 00:002:10:36:53 |
| Block: 6576 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1321 | RingCT/type: yes/0 |
| Extra: 0116a9b3d1f2b8d06a0cc06a8a0d891bd6f3f9458edef08e19742de64156318a92020900000001e49593ff00 | ||
1 output(s) for total of 34.745886122947 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f5c599778d944cfb1bd2df0eb15ee056edecb4f248fa3fe61a0155c15f3dad1 | 34.745886122947 | 8100 of 0 | <0d> |
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": 6636,
"vin": [ {
"gen": {
"height": 6576
}
}
],
"vout": [ {
"amount": 34745886122947,
"target": {
"tagged_key": {
"key": "7f5c599778d944cfb1bd2df0eb15ee056edecb4f248fa3fe61a0155c15f3dad1",
"view_tag": "0d"
}
}
}
],
"extra": [ 1, 22, 169, 179, 209, 242, 184, 208, 106, 12, 192, 106, 138, 13, 137, 27, 214, 243, 249, 69, 142, 222, 240, 142, 25, 116, 45, 230, 65, 86, 49, 138, 146, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}