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: ec39638156c366d3d35bc65a1f97c5b2c9b81f333d0b3c267babb9752ebe04b7
Tx prefix hash: 9a98c51c029d2953dc45ee023fa72d15b3212d8bb35fff5a504dcaa14aa3635b
Tx public key: 9f7ffa20653d42140dc8d8b78df1bacd2768e4acfec0efef9b82314f5b693ddf
| Timestamp: 1780896962 | Timestamp [UTC]: 2026-06-08 05:36:02 | Age [y:d:h:m:s]: 00:000:19:10:45 |
| Block: 7772 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 114 | RingCT/type: yes/0 |
| Extra: 019f7ffa20653d42140dc8d8b78df1bacd2768e4acfec0efef9b82314f5b693ddf0209000000034a728a4c00 | ||
1 output(s) for total of 34.666714452549 HMNY
| stealth address | amount | amount idx | tag |
| 00: a90357b9509adf23df62c2b1de1d32f32f1e526bc417bb562fdba885a0fa9a1e | 34.666714452549 | 9630 of 0 | <d5> |
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": 7832,
"vin": [ {
"gen": {
"height": 7772
}
}
],
"vout": [ {
"amount": 34666714452549,
"target": {
"tagged_key": {
"key": "a90357b9509adf23df62c2b1de1d32f32f1e526bc417bb562fdba885a0fa9a1e",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 159, 127, 250, 32, 101, 61, 66, 20, 13, 200, 216, 183, 141, 241, 186, 205, 39, 104, 228, 172, 254, 192, 239, 239, 155, 130, 49, 79, 91, 105, 61, 223, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}