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: d7e466d09d7d526f4e274955d654e14e23be68444443db3a747b544d51ed26f2
Tx prefix hash: 6e9702d71435e7898aa13080859dca613ca854087e5bf2885d75e2306f948b51
Tx public key: 6dad1ff7dcb6c17ba3e0f6debca311ae55c26a724657357bc0388b85d8386190
| Timestamp: 1780021355 | Timestamp [UTC]: 2026-05-29 02:22:35 | Age [y:d:h:m:s]: 00:011:00:18:01 |
| Block: 4145 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3751 | RingCT/type: yes/0 |
| Extra: 016dad1ff7dcb6c17ba3e0f6debca311ae55c26a724657357bc0388b85d838619002090000000126697be300 | ||
1 output(s) for total of 34.907368858554 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7bd4659c6d1d6a47e372db5b549c0a0b455ca25235cdf0922e5ad34e3d0700ae | 34.907368858554 | 5176 of 0 | <fe> |
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": 4205,
"vin": [ {
"gen": {
"height": 4145
}
}
],
"vout": [ {
"amount": 34907368858554,
"target": {
"tagged_key": {
"key": "7bd4659c6d1d6a47e372db5b549c0a0b455ca25235cdf0922e5ad34e3d0700ae",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 109, 173, 31, 247, 220, 182, 193, 123, 163, 224, 246, 222, 188, 163, 17, 174, 85, 194, 106, 114, 70, 87, 53, 123, 192, 56, 139, 133, 216, 56, 97, 144, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}